[32m* 19-02:21:15 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 19-02:21:15 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 19-02:21:15 (3362) [INFO] [0m
[32m* 19-02:21:15 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 19-02:21:15 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 19-02:21:15 (3372) [INFO]               : epel extras updates[0m
[32m* 19-02:21:15 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 19-02:21:15 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 19-02:21:15 (3382) [INFO] [0m
[32m* 19-02:21:15 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 19-02:21:15 (3362) [INFO] [0m
[32m* 19-02:21:15 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 19-02:21:16 (3372) [INFO] Determining fastest mirrors[0m
[32m* 19-02:21:21 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 19-02:21:21 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 19-02:21:21 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 19-02:21:21 (3372) [INFO]  * base: mirror.natro.com[0m
[32m* 19-02:21:21 (3372) [INFO]  * epel: mirror.yer.az[0m
[32m* 19-02:21:21 (3372) [INFO]  * extras: mirror.natro.com[0m
[32m* 19-02:21:21 (3372) [INFO]  * updates: mirror.natro.com[0m
[32m* 19-02:21:47 (3382) [INFO] [0m
[32m* 19-02:21:47 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 19-02:21:47 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 19-02:21:47 (3362) [INFO] [0m
[32m* 19-02:21:47 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 19-02:21:48 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 19-02:21:48 (3382) [INFO] [0m
[32m* 19-02:21:48 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 19-02:21:48 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 19-02:21:51 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-19_02:21:51_modified_for_AlmaLinux_8.json[0m
[33m* 19-02:21: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 19-02:21:52 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 20-02:13:01 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 20-02:13:01 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 20-02:13:01 (3362) [INFO] [0m
[32m* 20-02:13:02 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 20-02:13:02 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 20-02:13:02 (3372) [INFO]               : epel extras updates[0m
[32m* 20-02:13:02 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 20-02:13:02 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 20-02:13:02 (3382) [INFO] [0m
[32m* 20-02:13:02 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 20-02:13:02 (3362) [INFO] [0m
[32m* 20-02:13:02 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 20-02:13:03 (3372) [INFO] Determining fastest mirrors[0m
[32m* 20-02:13:09 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 20-02:13:09 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 20-02:13:09 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 20-02:13:09 (3372) [INFO]  * base: mirror.natro.com[0m
[32m* 20-02:13:09 (3372) [INFO]  * epel: mirror.yer.az[0m
[32m* 20-02:13:09 (3372) [INFO]  * extras: mirror.natro.com[0m
[32m* 20-02:13:09 (3372) [INFO]  * updates: mirror.natro.com[0m
[32m* 20-02:13:32 (3382) [INFO] [0m
[32m* 20-02:13:32 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 20-02:13:32 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 20-02:13:32 (3362) [INFO] [0m
[32m* 20-02:13:32 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 20-02:13:34 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 20-02:13:34 (3382) [INFO] [0m
[32m* 20-02:13:34 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 20-02:13:34 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 20-02:13:35 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-20_02:13:35_modified_for_AlmaLinux_8.json[0m
[33m* 20-02:13: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 20-02:13:37 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 21-02:12:57 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 21-02:12:57 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 21-02:12:57 (3362) [INFO] [0m
[32m* 21-02:12:57 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 21-02:12:57 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 21-02:12:57 (3372) [INFO]               : epel extras updates[0m
[32m* 21-02:12:58 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 21-02:12:58 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 21-02:12:58 (3382) [INFO] [0m
[32m* 21-02:12:58 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 21-02:12:58 (3362) [INFO] [0m
[32m* 21-02:12:59 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 21-02:12:59 (3372) [INFO] Determining fastest mirrors[0m
[32m* 21-02:13:05 (3372) [INFO]  * EA4: 178.18.193.52[0m
[32m* 21-02:13:05 (3372) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 21-02:13:05 (3372) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 21-02:13:05 (3372) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 21-02:13:05 (3372) [INFO]  * epel: mirror.yer.az[0m
[32m* 21-02:13:05 (3372) [INFO]  * extras: mirror.netdirekt.com.tr[0m
[32m* 21-02:13:05 (3372) [INFO]  * updates: mirror.natro.com[0m
[32m* 21-02:13:30 (3382) [INFO] [0m
[32m* 21-02:13:30 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 21-02:13:30 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 21-02:13:30 (3362) [INFO] [0m
[32m* 21-02:13:31 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 21-02:13:32 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 21-02:13:32 (3382) [INFO] [0m
[32m* 21-02:13:32 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 21-02:13:32 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 21-02:13:33 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-21_02:13:33_modified_for_AlmaLinux_8.json[0m
[33m* 21-02:13: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 21-02:13:35 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 22-02:13:34 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 22-02:13:34 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 22-02:13:34 (3362) [INFO] [0m
[32m* 22-02:13:34 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 22-02:13:34 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 22-02:13:34 (3372) [INFO]               : epel extras updates[0m
[32m* 22-02:13:35 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 22-02:13:35 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 22-02:13:35 (3382) [INFO] [0m
[32m* 22-02:13:35 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 22-02:13:35 (3362) [INFO] [0m
[32m* 22-02:13:35 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 22-02:13:35 (3372) [INFO] Determining fastest mirrors[0m
[32m* 22-02:13:41 (3372) [INFO]  * EA4: 178.18.193.52[0m
[32m* 22-02:13:41 (3372) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 22-02:13:41 (3372) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 22-02:13:41 (3372) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 22-02:13:41 (3372) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 22-02:13:41 (3372) [INFO]  * extras: mirror.natro.com[0m
[32m* 22-02:13:41 (3372) [INFO]  * updates: mirror.natro.com[0m
[32m* 22-02:14:04 (3382) [INFO] [0m
[32m* 22-02:14:04 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 22-02:14:04 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 22-02:14:04 (3362) [INFO] [0m
[32m* 22-02:14:04 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 22-02:14:05 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 22-02:14:05 (3382) [INFO] [0m
[32m* 22-02:14:05 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 22-02:14:05 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 22-02:14:07 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-22_02:14:07_modified_for_AlmaLinux_8.json[0m
[33m* 22-02:14:07 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 22-02:14:09 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 23-02:13:43 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 23-02:13:43 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 23-02:13:43 (3362) [INFO] [0m
[32m* 23-02:13:43 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 23-02:13:43 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 23-02:13:43 (3372) [INFO]               : epel extras updates[0m
[32m* 23-02:13:44 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 23-02:13:44 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 23-02:13:44 (3382) [INFO] [0m
[32m* 23-02:13:44 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 23-02:13:44 (3362) [INFO] [0m
[32m* 23-02:13:44 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 23-02:13:44 (3372) [INFO] Determining fastest mirrors[0m
[32m* 23-02:13:49 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 23-02:13:49 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 23-02:13:49 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 23-02:13:49 (3372) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 23-02:13:49 (3372) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 23-02:13:49 (3372) [INFO]  * extras: mirror.natro.com[0m
[32m* 23-02:13:49 (3372) [INFO]  * updates: mirror.natro.com[0m
[32m* 23-02:14:22 (3382) [INFO] [0m
[32m* 23-02:14:22 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 23-02:14:22 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 23-02:14:22 (3362) [INFO] [0m
[32m* 23-02:14:23 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 23-02:14:24 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 23-02:14:24 (3382) [INFO] [0m
[32m* 23-02:14:24 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 23-02:14:24 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 23-02:14:25 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-23_02:14:25_modified_for_AlmaLinux_8.json[0m
[33m* 23-02:14: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 23-02:14:27 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 23-15:47:05 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 23-15:47:05 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 23-15:47:05 (3362) [INFO] [0m
[32m* 23-15:47:05 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 23-15:47:06 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 23-15:47:06 (3372) [INFO]               : epel extras updates[0m
[32m* 23-15:47:06 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 23-15:47:06 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 23-15:47:06 (3382) [INFO] [0m
[32m* 23-15:47:06 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 23-15:47:06 (3362) [INFO] [0m
[32m* 23-15:47:06 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 23-15:47:07 (3372) [INFO] Determining fastest mirrors[0m
[32m* 23-15:47:13 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 23-15:47:13 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 23-15:47:13 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 23-15:47:13 (3372) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 23-15:47:13 (3372) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 23-15:47:13 (3372) [INFO]  * extras: mirror.natro.com[0m
[32m* 23-15:47:13 (3372) [INFO]  * updates: mirrors.binaryracks.com[0m
[32m* 23-15:47:47 (3382) [INFO] [0m
[32m* 23-15:47:47 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 23-15:47:47 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 23-15:47:47 (3362) [INFO] [0m
[32m* 23-15:47:48 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 23-15:47:49 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 23-15:47:49 (3382) [INFO] [0m
[32m* 23-15:47:49 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 23-15:47:49 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 23-15:47:50 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-23_15:47:50_modified_for_AlmaLinux_8.json[0m
[33m* 23-15:47: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 23-15:47:51 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 24-02:14:17 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 24-02:14:17 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 24-02:14:17 (3362) [INFO] [0m
[32m* 24-02:14:17 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 24-02:14:18 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 24-02:14:18 (3372) [INFO]               : epel extras updates[0m
[32m* 24-02:14:18 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 24-02:14:18 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 24-02:14:18 (3382) [INFO] [0m
[32m* 24-02:14:18 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 24-02:14:18 (3362) [INFO] [0m
[32m* 24-02:14:18 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 24-02:14:19 (3372) [INFO] Determining fastest mirrors[0m
[32m* 24-02:14:23 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 24-02:14:23 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 24-02:14:23 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 24-02:14:23 (3372) [INFO]  * base: centos.vargonen.com[0m
[32m* 24-02:14:23 (3372) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 24-02:14:23 (3372) [INFO]  * extras: mirror.netdirekt.com.tr[0m
[32m* 24-02:14:23 (3372) [INFO]  * updates: mirror.natro.com[0m
[32m* 24-02:14:46 (3382) [INFO] [0m
[32m* 24-02:14:46 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 24-02:14:46 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 24-02:14:46 (3362) [INFO] [0m
[32m* 24-02:14:46 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 24-02:14:47 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 24-02:14:47 (3382) [INFO] [0m
[32m* 24-02:14:47 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 24-02:14:47 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 24-02:14:49 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-24_02:14:49_modified_for_AlmaLinux_8.json[0m
[33m* 24-02:14:49 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 24-02:14:50 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 25-02:14:34 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 25-02:14:34 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 25-02:14:34 (3362) [INFO] [0m
[32m* 25-02:14:34 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 25-02:14:34 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 25-02:14:34 (3372) [INFO]               : epel extras updates[0m
[32m* 25-02:14:35 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 25-02:14:35 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 25-02:14:35 (3382) [INFO] [0m
[32m* 25-02:14:35 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 25-02:14:35 (3362) [INFO] [0m
[32m* 25-02:14:35 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 25-02:14:36 (3372) [INFO] Determining fastest mirrors[0m
[32m* 25-02:14:48 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 25-02:14:48 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 25-02:14:48 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 25-02:14:48 (3372) [INFO]  * base: mirror.natro.com[0m
[32m* 25-02:14:48 (3372) [INFO]  * epel: mirror.yer.az[0m
[32m* 25-02:14:48 (3372) [INFO]  * extras: mirror.onlinehosting.com.tr[0m
[32m* 25-02:14:48 (3372) [INFO]  * updates: mirror.netdirekt.com.tr[0m
[32m* 25-02:15:14 (3382) [INFO] [0m
[32m* 25-02:15:14 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 25-02:15:14 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 25-02:15:14 (3362) [INFO] [0m
[32m* 25-02:15:14 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 25-02:15:15 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 25-02:15:15 (3382) [INFO] [0m
[32m* 25-02:15:15 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 25-02:15:15 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 25-02:15:16 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-25_02:15:16_modified_for_AlmaLinux_8.json[0m
[33m* 25-02:15:16 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 25-02:15:18 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 26-02:13:15 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 26-02:13:15 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 26-02:13:15 (3362) [INFO] [0m
[32m* 26-02:13:15 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 26-02:13:16 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 26-02:13:16 (3372) [INFO]               : epel extras updates[0m
[32m* 26-02:13:16 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 26-02:13:16 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 26-02:13:16 (3382) [INFO] [0m
[32m* 26-02:13:16 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 26-02:13:16 (3362) [INFO] [0m
[32m* 26-02:13:16 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 26-02:13:17 (3372) [INFO] Determining fastest mirrors[0m
[32m* 26-02:13:23 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 26-02:13:23 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 26-02:13:23 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 26-02:13:23 (3372) [INFO]  * base: mirror.netdirekt.com.tr[0m
[32m* 26-02:13:23 (3372) [INFO]  * epel: mirror.yer.az[0m
[32m* 26-02:13:23 (3372) [INFO]  * extras: mirror.natro.com[0m
[32m* 26-02:13:23 (3372) [INFO]  * updates: mirror.natro.com[0m
[32m* 26-02:13:51 (3382) [INFO] [0m
[32m* 26-02:13:51 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 26-02:13:51 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 26-02:13:51 (3362) [INFO] [0m
[32m* 26-02:13:51 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 26-02:13:53 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 26-02:13:53 (3382) [INFO] [0m
[32m* 26-02:13:53 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 26-02:13:53 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 26-02:13:55 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-26_02:13:55_modified_for_AlmaLinux_8.json[0m
[33m* 26-02:13:55 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 26-02:13:57 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 27-02:28:05 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 27-02:28:05 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 27-02:28:05 (3362) [INFO] [0m
[32m* 27-02:28:05 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 27-02:28:06 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 27-02:28:06 (3372) [INFO]               : epel extras updates[0m
[32m* 27-02:28:06 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 27-02:28:06 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 27-02:28:06 (3382) [INFO] [0m
[32m* 27-02:28:06 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 27-02:28:06 (3362) [INFO] [0m
[32m* 27-02:28:06 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 27-02:28:07 (3372) [INFO] Determining fastest mirrors[0m
[32m* 27-02:28:11 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 27-02:28:11 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 27-02:28:11 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 27-02:28:11 (3372) [INFO]  * base: mirror.natro.com[0m
[32m* 27-02:28:11 (3372) [INFO]  * epel: mirror.ps.kz[0m
[32m* 27-02:28:11 (3372) [INFO]  * extras: mirror.netdirekt.com.tr[0m
[32m* 27-02:28:11 (3372) [INFO]  * updates: mirror.natro.com[0m
[32m* 27-02:28:41 (3382) [INFO] [0m
[32m* 27-02:28:41 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 27-02:28:41 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 27-02:28:41 (3362) [INFO] [0m
[32m* 27-02:28:41 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 27-02:28:42 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 27-02:28:42 (3382) [INFO] [0m
[32m* 27-02:28:42 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 27-02:28:42 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 27-02:28:43 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-27_02:28:43_modified_for_AlmaLinux_8.json[0m
[33m* 27-02:28:43 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 27-02:28:44 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 28-02:12:43 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 28-02:12:43 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 28-02:12:43 (3362) [INFO] [0m
[32m* 28-02:12:44 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 28-02:12:44 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 28-02:12:44 (3372) [INFO]               : epel extras updates[0m
[32m* 28-02:12:44 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 28-02:12:44 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 28-02:12:44 (3382) [INFO] [0m
[32m* 28-02:12:44 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 28-02:12:44 (3362) [INFO] [0m
[32m* 28-02:12:44 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 28-02:12:45 (3372) [INFO] Determining fastest mirrors[0m
[32m* 28-02:12:50 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 28-02:12:50 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 28-02:12:50 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 28-02:12:50 (3372) [INFO]  * base: mirror.netdirekt.com.tr[0m
[32m* 28-02:12:50 (3372) [INFO]  * epel: mirror.yer.az[0m
[32m* 28-02:12:50 (3372) [INFO]  * extras: mirror.netdirekt.com.tr[0m
[32m* 28-02:12:50 (3372) [INFO]  * updates: mirror.netdirekt.com.tr[0m
[32m* 28-02:13:17 (3382) [INFO] [0m
[32m* 28-02:13:17 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 28-02:13:17 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 28-02:13:17 (3362) [INFO] [0m
[32m* 28-02:13:18 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 28-02:13:19 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 28-02:13:19 (3382) [INFO] [0m
[32m* 28-02:13:19 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 28-02:13:19 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 28-02:13:20 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-28_02:13:20_modified_for_AlmaLinux_8.json[0m
[33m* 28-02:13:20 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 28-02:13:21 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 29-02:13:13 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 29-02:13:13 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 29-02:13:13 (3362) [INFO] [0m
[32m* 29-02:13:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 29-02:13:14 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 29-02:13:14 (3372) [INFO]               : epel extras updates[0m
[32m* 29-02:13:14 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 29-02:13:14 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 29-02:13:14 (3382) [INFO] [0m
[32m* 29-02:13:14 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 29-02:13:14 (3362) [INFO] [0m
[32m* 29-02:13:14 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 29-02:13:15 (3372) [INFO] Determining fastest mirrors[0m
[32m* 29-02:13:19 (3372) [INFO]  * EA4: 178.18.193.52[0m
[32m* 29-02:13:19 (3372) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 29-02:13:19 (3372) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 29-02:13:19 (3372) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 29-02:13:19 (3372) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 29-02:13:19 (3372) [INFO]  * extras: mirror.natro.com[0m
[32m* 29-02:13:19 (3372) [INFO]  * updates: mirror.natro.com[0m
[32m* 29-02:13:46 (3382) [INFO] [0m
[32m* 29-02:13:46 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 29-02:13:46 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 29-02:13:46 (3362) [INFO] [0m
[32m* 29-02:13:46 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 29-02:13:47 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 29-02:13:47 (3382) [INFO] [0m
[32m* 29-02:13:47 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 29-02:13:47 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 29-02:13:50 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-29_02:13:50_modified_for_AlmaLinux_8.json[0m
[33m* 29-02:13: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 29-02:13:51 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 30-02:13:32 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 30-02:13:32 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 30-02:13:32 (3362) [INFO] [0m
[32m* 30-02:13:33 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 30-02:13:33 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 30-02:13:33 (3372) [INFO]               : epel extras updates[0m
[32m* 30-02:13:33 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 30-02:13:33 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 30-02:13:33 (3382) [INFO] [0m
[32m* 30-02:13:33 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 30-02:13:33 (3362) [INFO] [0m
[32m* 30-02:13:34 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 30-02:13:34 (3372) [INFO] Determining fastest mirrors[0m
[32m* 30-02:13:38 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 30-02:13:38 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 30-02:13:38 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 30-02:13:38 (3372) [INFO]  * base: mirror.natro.com[0m
[32m* 30-02:13:38 (3372) [INFO]  * epel: ftp.iij.ad.jp[0m
[32m* 30-02:13:38 (3372) [INFO]  * extras: mirror.natro.com[0m
[32m* 30-02:13:38 (3372) [INFO]  * updates: mirror.natro.com[0m
[32m* 30-02:14:08 (3382) [INFO] [0m
[32m* 30-02:14:08 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 30-02:14:08 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 30-02:14:08 (3362) [INFO] [0m
[32m* 30-02:14:09 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 30-02:14:11 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 30-02:14:11 (3382) [INFO] [0m
[32m* 30-02:14:11 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 30-02:14:11 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 30-02:14:13 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-30_02:14:13_modified_for_AlmaLinux_8.json[0m
[33m* 30-02:14:13 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 30-02:14:14 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 30-15:47:50 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 30-15:47:50 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 30-15:47:50 (3362) [INFO] [0m
[32m* 30-15:47:50 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 30-15:47:50 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 30-15:47:50 (3372) [INFO]               : epel extras updates[0m
[32m* 30-15:47:50 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 30-15:47:50 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 30-15:47:50 (3382) [INFO] [0m
[32m* 30-15:47:50 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 30-15:47:50 (3362) [INFO] [0m
[32m* 30-15:47:51 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 30-15:47:51 (3372) [INFO] Determining fastest mirrors[0m
[32m* 30-15:47:55 (3372) [INFO]  * EA4: 178.18.193.52[0m
[32m* 30-15:47:55 (3372) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 30-15:47:55 (3372) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 30-15:47:55 (3372) [INFO]  * base: mirror.natro.com[0m
[32m* 30-15:47:55 (3372) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 30-15:47:55 (3372) [INFO]  * extras: mirror.natro.com[0m
[32m* 30-15:47:55 (3372) [INFO]  * updates: mirror.natro.com[0m
[32m* 30-15:48:17 (3382) [INFO] [0m
[32m* 30-15:48:17 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 30-15:48:17 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 30-15:48:17 (3362) [INFO] [0m
[32m* 30-15:48:17 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 30-15:48:18 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 30-15:48:18 (3382) [INFO] [0m
[32m* 30-15:48:18 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 30-15:48:18 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 30-15:48:19 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-30_15:48:19_modified_for_AlmaLinux_8.json[0m
[33m* 30-15:48:19 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 30-15:48:26 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 01-02:13:42 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 01-02:13:42 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 01-02:13:42 (3362) [INFO] [0m
[32m* 01-02:13:42 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 01-02:13:42 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 01-02:13:42 (3372) [INFO]               : epel extras updates[0m
[32m* 01-02:13:42 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 01-02:13:42 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 01-02:13:43 (3382) [INFO] [0m
[32m* 01-02:13:43 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 01-02:13:43 (3362) [INFO] [0m
[32m* 01-02:13:43 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 01-02:13:43 (3372) [INFO] Determining fastest mirrors[0m
[32m* 01-02:13:49 (3372) [INFO]  * EA4: 178.18.193.52[0m
[32m* 01-02:13:49 (3372) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 01-02:13:49 (3372) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 01-02:13:49 (3372) [INFO]  * base: mirror.natro.com[0m
[32m* 01-02:13:49 (3372) [INFO]  * epel: mirror.yer.az[0m
[32m* 01-02:13:49 (3372) [INFO]  * extras: mirror.natro.com[0m
[32m* 01-02:13:49 (3372) [INFO]  * updates: mirror.natro.com[0m
[32m* 01-02:14:16 (3382) [INFO] [0m
[32m* 01-02:14:16 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 01-02:14:16 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 01-02:14:16 (3362) [INFO] [0m
[32m* 01-02:14:16 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 01-02:14:18 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 01-02:14:18 (3382) [INFO] [0m
[32m* 01-02:14:18 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 01-02:14:18 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 01-02:14:19 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-01_02:14:19_modified_for_AlmaLinux_8.json[0m
[33m* 01-02:14:19 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 01-02:14:20 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 02-02:15:28 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 02-02:15:28 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 02-02:15:28 (3362) [INFO] [0m
[32m* 02-02:15:28 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 02-02:15:28 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 02-02:15:28 (3372) [INFO]               : epel extras updates[0m
[32m* 02-02:15:29 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 02-02:15:29 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 02-02:15:29 (3382) [INFO] [0m
[32m* 02-02:15:29 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 02-02:15:29 (3362) [INFO] [0m
[32m* 02-02:15:29 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 02-02:15:29 (3372) [INFO] Determining fastest mirrors[0m
[32m* 02-02:15:35 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 02-02:15:35 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 02-02:15:35 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 02-02:15:35 (3372) [INFO]  * base: mirror.natro.com[0m
[32m* 02-02:15:35 (3372) [INFO]  * epel: mirror.ps.kz[0m
[32m* 02-02:15:35 (3372) [INFO]  * extras: mirror.netdirekt.com.tr[0m
[32m* 02-02:15:35 (3372) [INFO]  * updates: mirror.netdirekt.com.tr[0m
[32m* 02-02:16:02 (3382) [INFO] [0m
[32m* 02-02:16:02 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 02-02:16:02 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 02-02:16:02 (3362) [INFO] [0m
[32m* 02-02:16:02 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 02-02:16:04 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 02-02:16:04 (3382) [INFO] [0m
[32m* 02-02:16:04 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 02-02:16:04 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 02-02:16:06 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-02_02:16:06_modified_for_AlmaLinux_8.json[0m
[33m* 02-02:16:06 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 02-02:16:07 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 03-02:13:38 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 03-02:13:38 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 03-02:13:38 (3362) [INFO] [0m
[32m* 03-02:13:39 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 03-02:13:39 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 03-02:13:39 (3372) [INFO]               : epel extras updates[0m
[32m* 03-02:13:39 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 03-02:13:39 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 03-02:13:39 (3382) [INFO] [0m
[32m* 03-02:13:39 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 03-02:13:39 (3362) [INFO] [0m
[32m* 03-02:13:39 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 03-02:13:40 (3372) [INFO] Determining fastest mirrors[0m
[32m* 03-02:13:45 (3372) [INFO]  * EA4: 178.18.193.52[0m
[32m* 03-02:13:45 (3372) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 03-02:13:45 (3372) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 03-02:13:45 (3372) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 03-02:13:45 (3372) [INFO]  * epel: mirror.ps.kz[0m
[32m* 03-02:13:45 (3372) [INFO]  * extras: mirror.natro.com[0m
[32m* 03-02:13:45 (3372) [INFO]  * updates: mirror.netdirekt.com.tr[0m
[32m* 03-02:14:14 (3382) [INFO] [0m
[32m* 03-02:14:14 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 03-02:14:14 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 03-02:14:14 (3362) [INFO] [0m
[32m* 03-02:14:15 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 03-02:14:16 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 03-02:14:16 (3382) [INFO] [0m
[32m* 03-02:14:16 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 03-02:14:16 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 03-02:14:17 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-03_02:14:17_modified_for_AlmaLinux_8.json[0m
[33m* 03-02:14: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 03-02:14:18 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 04-02:14:57 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 04-02:14:57 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 04-02:14:57 (3362) [INFO] [0m
[32m* 04-02:14:58 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 04-02:14:58 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 04-02:14:58 (3372) [INFO]               : epel extras updates[0m
[32m* 04-02:14:58 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 04-02:14:58 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 04-02:14:58 (3382) [INFO] [0m
[32m* 04-02:14:58 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 04-02:14:58 (3362) [INFO] [0m
[32m* 04-02:14:58 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 04-02:14:59 (3372) [INFO] Determining fastest mirrors[0m
[32m* 04-02:15:04 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 04-02:15:04 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 04-02:15:04 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 04-02:15:04 (3372) [INFO]  * base: mirror.natro.com[0m
[32m* 04-02:15:04 (3372) [INFO]  * epel: mirror.yer.az[0m
[32m* 04-02:15:04 (3372) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 04-02:15:04 (3372) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 04-02:15:24 (3382) [INFO] [0m
[32m* 04-02:15:24 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 04-02:15:24 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 04-02:15:24 (3362) [INFO] [0m
[32m* 04-02:15:24 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 04-02:15:25 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 04-02:15:25 (3382) [INFO] [0m
[32m* 04-02:15:25 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 04-02:15:25 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 04-02:15:27 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-04_02:15:27_modified_for_AlmaLinux_8.json[0m
[33m* 04-02:15: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 04-02:15:28 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 05-02:15:49 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 05-02:15:50 (3077) [ERROR] http://centosa9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosa9.centos.org:80; Connection refused"
Trying other mirror.
http://centosg8.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosg8.centos.org:80; Connection refused"
Trying other mirror.
http://centosf6.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosf6.centos.org:80; Connection refused"
Trying other mirror.
http://centosg9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2401:78c0::e00e: Network is unreachable"
Trying other mirror.
http://centosk9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2605:9000:401:103::2: Network is unreachable"
Trying other mirror.
http://centosj9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2001:67c:744:2::10: Network is unreachable"
Trying other mirror.
http://centosh7.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2c0f:f738:2201:e::: Network is unreachable"
Trying other mirror.
http://centosz3.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:eb80:1:4::10: Network is unreachable"
Trying other mirror.
http://centosm7.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:1580:fe02:2::10: Network is unreachable"
Trying other mirror.
http://mirror.s8.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2607:ff28:800f:13f:5054:ff:fe6b:2a18: Network is unreachable"
Trying other mirror.


 One of the configured repositories failed (CentOS-7 - Extras),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=extras ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable extras
        or
            subscription-manager repos --disable=extras

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=extras.skip_if_unavailable=true

failure: repodata/repomd.xml from extras: [Errno 256] No more mirrors to try.
http://centosa9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosa9.centos.org:80; Connection refused"
http://centosg8.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosg8.centos.org:80; Connection refused"
http://centosf6.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosf6.centos.org:80; Connection refused"
http://centosg9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2401:78c0::e00e: Network is unreachable"
http://centosk9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2605:9000:401:103::2: Network is unreachable"
http://centosj9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2001:67c:744:2::10: Network is unreachable"
http://centosh7.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2c0f:f738:2201:e::: Network is unreachable"
http://centosz3.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:eb80:1:4::10: Network is unreachable"
http://centosm7.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:1580:fe02:2::10: Network is unreachable"
http://mirror.s8.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2607:ff28:800f:13f:5054:ff:fe6b:2a18: Network is unreachable"
[0m
[33m* 05-02:15:50 (2504) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 05-02:15:51 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 05-02:15:51 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 05-02:15:51 (3362) [INFO] [0m
[32m* 05-02:15:51 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 05-02:15:51 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 05-02:15:51 (3372) [INFO]               : epel extras updates[0m
[32m* 05-02:15:51 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 05-02:15:51 (3372) [INFO] Other repos take up 424 k of disk space (use --verbose for details)[0m
[32m* 05-02:15:51 (3382) [INFO] [0m
[32m* 05-02:15:51 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 05-02:15:51 (3362) [INFO] [0m
[32m* 05-02:15:52 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 05-02:15:52 (3372) [INFO] Determining fastest mirrors[0m
[32m* 05-02:15:58 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 05-02:15:58 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 05-02:15:58 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 05-02:15:58 (3372) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 05-02:15:58 (3372) [INFO]  * epel: mirror.ps.kz[0m
[32m* 05-02:15:58 (3372) [INFO]  * extras: centosa9.centos.org[0m
[32m* 05-02:15:58 (3372) [INFO]  * updates: mirror.natro.com[0m
[32m* 05-02:16:00 (3372) [INFO] http://centosa9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosa9.centos.org:80; Connection refused"[0m
[32m* 05-02:16:00 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:01 (3372) [INFO] http://centosg8.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosg8.centos.org:80; Connection refused"[0m
[32m* 05-02:16:01 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:01 (3372) [INFO] http://centosf6.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosf6.centos.org:80; Connection refused"[0m
[32m* 05-02:16:01 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:01 (3372) [INFO] http://centosg9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2401:78c0::e00e: Network is unreachable"[0m
[32m* 05-02:16:01 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:02 (3372) [INFO] http://centosk9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2605:9000:401:103::2: Network is unreachable"[0m
[32m* 05-02:16:02 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:02 (3372) [INFO] http://centosj9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2001:67c:744:2::10: Network is unreachable"[0m
[32m* 05-02:16:02 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:03 (3372) [INFO] http://centosh7.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2c0f:f738:2201:e::: Network is unreachable"[0m
[32m* 05-02:16:03 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:03 (3372) [INFO] http://centosz3.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:eb80:1:4::10: Network is unreachable"[0m
[32m* 05-02:16:03 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:03 (3372) [INFO] http://centosm7.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:1580:fe02:2::10: Network is unreachable"[0m
[32m* 05-02:16:03 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:03 (3372) [INFO] http://mirror.s8.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2607:ff28:800f:13f:5054:ff:fe6b:2a18: Network is unreachable"[0m
[32m* 05-02:16:03 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:03 (3372) [INFO] [0m
[32m* 05-02:16:03 (3372) [INFO] [0m
[32m* 05-02:16:03 (3372) [INFO]  One of the configured repositories failed (CentOS-7 - Extras),[0m
[32m* 05-02:16:03 (3372) [INFO]  and yum doesn't have enough cached data to continue. At this point the only[0m
[32m* 05-02:16:03 (3372) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:[0m
[32m* 05-02:16:03 (3372) [INFO] [0m
[32m* 05-02:16:03 (3372) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.[0m
[32m* 05-02:16:03 (3372) [INFO] [0m
[32m* 05-02:16:03 (3372) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working[0m
[32m* 05-02:16:03 (3372) [INFO]         upstream. This is most often useful if you are using a newer[0m
[32m* 05-02:16:03 (3372) [INFO]         distribution release than is supported by the repository (and the[0m
[32m* 05-02:16:03 (3372) [INFO]         packages for the previous distribution release still work).[0m
[32m* 05-02:16:03 (3372) [INFO] [0m
[32m* 05-02:16:03 (3372) [INFO]      3. Run the command with the repository temporarily disabled[0m
[32m* 05-02:16:03 (3372) [INFO]             yum --disablerepo=extras ...[0m
[32m* 05-02:16:03 (3372) [INFO] [0m
[32m* 05-02:16:03 (3372) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum[0m
[32m* 05-02:16:03 (3372) [INFO]         will then just ignore the repository until you permanently enable it[0m
[32m* 05-02:16:03 (3372) [INFO]         again or use --enablerepo for temporary usage:[0m
[32m* 05-02:16:03 (3372) [INFO] [0m
[32m* 05-02:16:03 (3372) [INFO]             yum-config-manager --disable extras[0m
[32m* 05-02:16:03 (3372) [INFO]         or[0m
[32m* 05-02:16:03 (3372) [INFO]             subscription-manager repos --disable=extras[0m
[32m* 05-02:16:03 (3372) [INFO] [0m
[32m* 05-02:16:03 (3372) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.[0m
[32m* 05-02:16:03 (3372) [INFO]         Note that yum will try to contact the repo. when it runs most commands,[0m
[32m* 05-02:16:03 (3372) [INFO]         so will have to try and fail each time (and thus. yum will be be much[0m
[32m* 05-02:16:03 (3372) [INFO]         slower). If it is a very temporary problem though, this is often a nice[0m
[32m* 05-02:16:03 (3372) [INFO]         compromise:[0m
[32m* 05-02:16:03 (3372) [INFO] [0m
[32m* 05-02:16:03 (3372) [INFO]             yum-config-manager --save --setopt=extras.skip_if_unavailable=true[0m
[32m* 05-02:16:03 (3372) [INFO] [0m
[32m* 05-02:16:03 (3372) [INFO] failure: repodata/repomd.xml from extras: [Errno 256] No more mirrors to try.[0m
[32m* 05-02:16:03 (3372) [INFO] http://centosa9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosa9.centos.org:80; Connection refused"[0m
[32m* 05-02:16:03 (3372) [INFO] http://centosg8.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosg8.centos.org:80; Connection refused"[0m
[32m* 05-02:16:03 (3372) [INFO] http://centosf6.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosf6.centos.org:80; Connection refused"[0m
[32m* 05-02:16:03 (3372) [INFO] http://centosg9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2401:78c0::e00e: Network is unreachable"[0m
[32m* 05-02:16:03 (3372) [INFO] http://centosk9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2605:9000:401:103::2: Network is unreachable"[0m
[32m* 05-02:16:03 (3372) [INFO] http://centosj9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2001:67c:744:2::10: Network is unreachable"[0m
[32m* 05-02:16:03 (3372) [INFO] http://centosh7.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2c0f:f738:2201:e::: Network is unreachable"[0m
[32m* 05-02:16:03 (3372) [INFO] http://centosz3.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:eb80:1:4::10: Network is unreachable"[0m
[32m* 05-02:16:03 (3372) [INFO] http://centosm7.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:1580:fe02:2::10: Network is unreachable"[0m
[32m* 05-02:16:03 (3372) [INFO] http://mirror.s8.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2607:ff28:800f:13f:5054:ff:fe6b:2a18: Network is unreachable"[0m
[32m* 05-02:16:03 (3382) [INFO] [0m
[33m* 05-02:16:03 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 05-02:16:03 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 05-02:16:03 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 05-02:16:03 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[33m* 05-02:16:12 (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.
[0m
[33m* 05-02:16:12 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 05-02:16:22 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 05-02:16:22 (3077) [ERROR] http://centosa9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosa9.centos.org:80; Connection refused"
Trying other mirror.
http://centosg8.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosg8.centos.org:80; Connection refused"
Trying other mirror.
http://centosf6.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosf6.centos.org:80; Connection refused"
Trying other mirror.
http://centosg9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2401:78c0::e00e: Network is unreachable"
Trying other mirror.
http://centosk9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2605:9000:401:103::2: Network is unreachable"
Trying other mirror.
http://centosj9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2001:67c:744:2::10: Network is unreachable"
Trying other mirror.
http://centosh7.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2c0f:f738:2201:e::: Network is unreachable"
Trying other mirror.
http://centosz3.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:eb80:1:4::10: Network is unreachable"
Trying other mirror.
http://centosm7.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:1580:fe02:2::10: Network is unreachable"
Trying other mirror.
http://mirror.s8.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2607:ff28:800f:13f:5054:ff:fe6b:2a18: Network is unreachable"
Trying other mirror.


 One of the configured repositories failed (CentOS-7 - Extras),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=extras ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable extras
        or
            subscription-manager repos --disable=extras

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=extras.skip_if_unavailable=true

failure: repodata/repomd.xml from extras: [Errno 256] No more mirrors to try.
http://centosa9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosa9.centos.org:80; Connection refused"
http://centosg8.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosg8.centos.org:80; Connection refused"
http://centosf6.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosf6.centos.org:80; Connection refused"
http://centosg9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2401:78c0::e00e: Network is unreachable"
http://centosk9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2605:9000:401:103::2: Network is unreachable"
http://centosj9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2001:67c:744:2::10: Network is unreachable"
http://centosh7.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2c0f:f738:2201:e::: Network is unreachable"
http://centosz3.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:eb80:1:4::10: Network is unreachable"
http://centosm7.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:1580:fe02:2::10: Network is unreachable"
http://mirror.s8.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2607:ff28:800f:13f:5054:ff:fe6b:2a18: Network is unreachable"
[0m
[33m* 05-02:16:22 (2504) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 05-02:16:23 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 05-02:16:23 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 05-02:16:23 (3362) [INFO] [0m
[32m* 05-02:16:23 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 05-02:16:23 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 05-02:16:23 (3372) [INFO]               : epel extras updates[0m
[32m* 05-02:16:23 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 05-02:16:23 (3372) [INFO] Other repos take up 424 k of disk space (use --verbose for details)[0m
[32m* 05-02:16:23 (3382) [INFO] [0m
[32m* 05-02:16:23 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 05-02:16:23 (3362) [INFO] [0m
[32m* 05-02:16:23 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 05-02:16:24 (3372) [INFO] Determining fastest mirrors[0m
[32m* 05-02:16:28 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 05-02:16:28 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 05-02:16:28 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 05-02:16:28 (3372) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 05-02:16:28 (3372) [INFO]  * epel: mirror.ps.kz[0m
[32m* 05-02:16:28 (3372) [INFO]  * extras: centosa9.centos.org[0m
[32m* 05-02:16:28 (3372) [INFO]  * updates: mirror.natro.com[0m
[32m* 05-02:16:31 (3372) [INFO] http://centosa9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosa9.centos.org:80; Connection refused"[0m
[32m* 05-02:16:31 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:31 (3372) [INFO] http://centosg8.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosg8.centos.org:80; Connection refused"[0m
[32m* 05-02:16:31 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:31 (3372) [INFO] http://centosf6.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosf6.centos.org:80; Connection refused"[0m
[32m* 05-02:16:31 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:31 (3372) [INFO] http://centosg9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2401:78c0::e00e: Network is unreachable"[0m
[32m* 05-02:16:31 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:32 (3372) [INFO] http://centosk9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2605:9000:401:103::2: Network is unreachable"[0m
[32m* 05-02:16:32 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:32 (3372) [INFO] http://centosj9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2001:67c:744:2::10: Network is unreachable"[0m
[32m* 05-02:16:32 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:32 (3372) [INFO] http://centosh7.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2c0f:f738:2201:e::: Network is unreachable"[0m
[32m* 05-02:16:32 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:32 (3372) [INFO] http://centosz3.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:eb80:1:4::10: Network is unreachable"[0m
[32m* 05-02:16:32 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:32 (3372) [INFO] http://centosm7.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:1580:fe02:2::10: Network is unreachable"[0m
[32m* 05-02:16:32 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:33 (3372) [INFO] http://mirror.s8.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2607:ff28:800f:13f:5054:ff:fe6b:2a18: Network is unreachable"[0m
[32m* 05-02:16:33 (3372) [INFO] Trying other mirror.[0m
[32m* 05-02:16:33 (3372) [INFO] [0m
[32m* 05-02:16:33 (3372) [INFO] [0m
[32m* 05-02:16:33 (3372) [INFO]  One of the configured repositories failed (CentOS-7 - Extras),[0m
[32m* 05-02:16:33 (3372) [INFO]  and yum doesn't have enough cached data to continue. At this point the only[0m
[32m* 05-02:16:33 (3372) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:[0m
[32m* 05-02:16:33 (3372) [INFO] [0m
[32m* 05-02:16:33 (3372) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.[0m
[32m* 05-02:16:33 (3372) [INFO] [0m
[32m* 05-02:16:33 (3372) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working[0m
[32m* 05-02:16:33 (3372) [INFO]         upstream. This is most often useful if you are using a newer[0m
[32m* 05-02:16:33 (3372) [INFO]         distribution release than is supported by the repository (and the[0m
[32m* 05-02:16:33 (3372) [INFO]         packages for the previous distribution release still work).[0m
[32m* 05-02:16:33 (3372) [INFO] [0m
[32m* 05-02:16:33 (3372) [INFO]      3. Run the command with the repository temporarily disabled[0m
[32m* 05-02:16:33 (3372) [INFO]             yum --disablerepo=extras ...[0m
[32m* 05-02:16:33 (3372) [INFO] [0m
[32m* 05-02:16:33 (3372) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum[0m
[32m* 05-02:16:33 (3372) [INFO]         will then just ignore the repository until you permanently enable it[0m
[32m* 05-02:16:33 (3372) [INFO]         again or use --enablerepo for temporary usage:[0m
[32m* 05-02:16:33 (3372) [INFO] [0m
[32m* 05-02:16:33 (3372) [INFO]             yum-config-manager --disable extras[0m
[32m* 05-02:16:33 (3372) [INFO]         or[0m
[32m* 05-02:16:33 (3372) [INFO]             subscription-manager repos --disable=extras[0m
[32m* 05-02:16:33 (3372) [INFO] [0m
[32m* 05-02:16:33 (3372) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.[0m
[32m* 05-02:16:33 (3372) [INFO]         Note that yum will try to contact the repo. when it runs most commands,[0m
[32m* 05-02:16:33 (3372) [INFO]         so will have to try and fail each time (and thus. yum will be be much[0m
[32m* 05-02:16:33 (3372) [INFO]         slower). If it is a very temporary problem though, this is often a nice[0m
[32m* 05-02:16:33 (3372) [INFO]         compromise:[0m
[32m* 05-02:16:33 (3372) [INFO] [0m
[32m* 05-02:16:33 (3372) [INFO]             yum-config-manager --save --setopt=extras.skip_if_unavailable=true[0m
[32m* 05-02:16:33 (3372) [INFO] [0m
[32m* 05-02:16:33 (3372) [INFO] failure: repodata/repomd.xml from extras: [Errno 256] No more mirrors to try.[0m
[32m* 05-02:16:33 (3372) [INFO] http://centosa9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosa9.centos.org:80; Connection refused"[0m
[32m* 05-02:16:33 (3372) [INFO] http://centosg8.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosg8.centos.org:80; Connection refused"[0m
[32m* 05-02:16:33 (3372) [INFO] http://centosf6.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to centosf6.centos.org:80; Connection refused"[0m
[32m* 05-02:16:33 (3372) [INFO] http://centosg9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2401:78c0::e00e: Network is unreachable"[0m
[32m* 05-02:16:33 (3372) [INFO] http://centosk9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2605:9000:401:103::2: Network is unreachable"[0m
[32m* 05-02:16:33 (3372) [INFO] http://centosj9.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2001:67c:744:2::10: Network is unreachable"[0m
[32m* 05-02:16:33 (3372) [INFO] http://centosh7.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2c0f:f738:2201:e::: Network is unreachable"[0m
[32m* 05-02:16:33 (3372) [INFO] http://centosz3.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:eb80:1:4::10: Network is unreachable"[0m
[32m* 05-02:16:33 (3372) [INFO] http://centosm7.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:1580:fe02:2::10: Network is unreachable"[0m
[32m* 05-02:16:33 (3372) [INFO] http://mirror.s8.centos.org/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2607:ff28:800f:13f:5054:ff:fe6b:2a18: Network is unreachable"[0m
[32m* 05-02:16:33 (3382) [INFO] [0m
[33m* 05-02:16:33 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 05-02:16:33 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 05-02:16:33 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 05-02:16:33 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[33m* 05-02:16:40 (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.
[0m
[33m* 05-02:16:40 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 06-02:33:01 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 06-02:33:02 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 06-02:33:02 (3362) [INFO] [0m
[32m* 06-02:33:02 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 06-02:33:02 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 06-02:33:02 (3372) [INFO]               : epel extras updates[0m
[32m* 06-02:33:02 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 06-02:33:02 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 06-02:33:02 (3382) [INFO] [0m
[32m* 06-02:33:02 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 06-02:33:02 (3362) [INFO] [0m
[32m* 06-02:33:03 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 06-02:33:03 (3372) [INFO] Determining fastest mirrors[0m
[32m* 06-02:33:20 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 06-02:33:20 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 06-02:33:20 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 06-02:33:20 (3372) [INFO]  * base: mirror.natro.com[0m
[32m* 06-02:33:20 (3372) [INFO]  * epel: mirror.ps.kz[0m
[32m* 06-02:33:20 (3372) [INFO]  * extras: mirror.natro.com[0m
[32m* 06-02:33:20 (3372) [INFO]  * updates: centos.vargonen.com[0m
[32m* 06-02:33:55 (3382) [INFO] [0m
[32m* 06-02:33:55 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 06-02:33:55 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 06-02:33:55 (3362) [INFO] [0m
[32m* 06-02:33:55 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 06-02:33:56 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 06-02:33:56 (3382) [INFO] [0m
[32m* 06-02:33:56 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 06-02:33:56 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 06-02:33:57 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-06_02:33:57_modified_for_AlmaLinux_8.json[0m
[33m* 06-02:33:57 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 06-02:33:59 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 07-02:22:37 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 07-02:22:37 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 07-02:22:37 (3362) [INFO] [0m
[32m* 07-02:22:37 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 07-02:22:37 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 07-02:22:37 (3372) [INFO]               : epel extras updates[0m
[32m* 07-02:22:38 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 07-02:22:38 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 07-02:22:38 (3382) [INFO] [0m
[32m* 07-02:22:38 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 07-02:22:38 (3362) [INFO] [0m
[32m* 07-02:22:38 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 07-02:22:38 (3372) [INFO] Determining fastest mirrors[0m
[32m* 07-02:22:42 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 07-02:22:42 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 07-02:22:42 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 07-02:22:42 (3372) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 07-02:22:42 (3372) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 07-02:22:42 (3372) [INFO]  * extras: mirror.natro.com[0m
[32m* 07-02:22:42 (3372) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 07-02:23:47 (3382) [INFO] [0m
[32m* 07-02:23:47 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 07-02:23:47 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 07-02:23:47 (3362) [INFO] [0m
[32m* 07-02:23:47 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 07-02:23:49 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 07-02:23:49 (3382) [INFO] [0m
[32m* 07-02:23:49 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 07-02:23:49 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 07-02:23:50 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-07_02:23:50_modified_for_AlmaLinux_8.json[0m
[33m* 07-02:23: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 07-02:23:51 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 07-15:51:06 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 07-15:51:07 (3077) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was
14: curl#7 - "Failed to connect to 2620:52:3:1:dead:beef:cafe:fed7: Network is unreachable"
[0m
[33m* 07-15:51:07 (2504) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 07-15:51:08 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 07-15:51:08 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 07-15:51:08 (3362) [INFO] [0m
[32m* 07-15:51:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 07-15:51:09 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 07-15:51:09 (3372) [INFO]               : epel extras updates[0m
[32m* 07-15:51:09 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 07-15:51:09 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 07-15:51:09 (3382) [INFO] [0m
[32m* 07-15:51:09 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 07-15:51:09 (3362) [INFO] [0m
[32m* 07-15:51:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 07-15:51:10 (3372) [INFO] Determining fastest mirrors[0m
[32m* 07-15:51:11 (3372) [INFO] [0m
[32m* 07-15:51:11 (3372) [INFO] [0m
[32m* 07-15:51:11 (3372) [INFO]  One of the configured repositories failed (Unknown),[0m
[32m* 07-15:51:11 (3372) [INFO]  and yum doesn't have enough cached data to continue. At this point the only[0m
[32m* 07-15:51:11 (3372) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:[0m
[32m* 07-15:51:11 (3372) [INFO] [0m
[32m* 07-15:51:11 (3372) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.[0m
[32m* 07-15:51:11 (3372) [INFO] [0m
[32m* 07-15:51:11 (3372) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working[0m
[32m* 07-15:51:11 (3372) [INFO]         upstream. This is most often useful if you are using a newer[0m
[32m* 07-15:51:11 (3372) [INFO]         distribution release than is supported by the repository (and the[0m
[32m* 07-15:51:11 (3372) [INFO]         packages for the previous distribution release still work).[0m
[32m* 07-15:51:11 (3372) [INFO] [0m
[32m* 07-15:51:11 (3372) [INFO]      3. Run the command with the repository temporarily disabled[0m
[32m* 07-15:51:11 (3372) [INFO]             yum --disablerepo=<repoid> ...[0m
[32m* 07-15:51:11 (3372) [INFO] [0m
[32m* 07-15:51:11 (3372) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum[0m
[32m* 07-15:51:11 (3372) [INFO]         will then just ignore the repository until you permanently enable it[0m
[32m* 07-15:51:11 (3372) [INFO]         again or use --enablerepo for temporary usage:[0m
[32m* 07-15:51:11 (3372) [INFO] [0m
[32m* 07-15:51:11 (3372) [INFO]             yum-config-manager --disable <repoid>[0m
[32m* 07-15:51:11 (3372) [INFO]         or[0m
[32m* 07-15:51:11 (3372) [INFO]             subscription-manager repos --disable=<repoid>[0m
[32m* 07-15:51:11 (3372) [INFO] [0m
[32m* 07-15:51:11 (3372) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.[0m
[32m* 07-15:51:11 (3372) [INFO]         Note that yum will try to contact the repo. when it runs most commands,[0m
[32m* 07-15:51:11 (3372) [INFO]         so will have to try and fail each time (and thus. yum will be be much[0m
[32m* 07-15:51:11 (3372) [INFO]         slower). If it is a very temporary problem though, this is often a nice[0m
[32m* 07-15:51:11 (3372) [INFO]         compromise:[0m
[32m* 07-15:51:11 (3372) [INFO] [0m
[32m* 07-15:51:11 (3372) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true[0m
[32m* 07-15:51:11 (3372) [INFO] [0m
[32m* 07-15:51:11 (3372) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again[0m
[32m* 07-15:51:12 (3382) [INFO] [0m
[33m* 07-15:51:12 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 07-15:51:12 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 07-15:51:12 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 07-15:51:12 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[33m* 07-15:51:15 (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.
[0m
[33m* 07-15:51:15 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 07-15:51:18 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 07-15:51:18 (3077) [ERROR] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
[0m
[33m* 07-15:51:18 (2504) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 07-15:51:18 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 07-15:51:18 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 07-15:51:18 (3362) [INFO] [0m
[32m* 07-15:51:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 07-15:51:19 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 07-15:51:19 (3372) [INFO]               : epel extras updates[0m
[32m* 07-15:51:19 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 07-15:51:19 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 07-15:51:19 (3382) [INFO] [0m
[32m* 07-15:51:19 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 07-15:51:19 (3362) [INFO] [0m
[32m* 07-15:51:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 07-15:51:20 (3372) [INFO] Determining fastest mirrors[0m
[32m* 07-15:51:21 (3372) [INFO] [0m
[32m* 07-15:51:21 (3372) [INFO] [0m
[32m* 07-15:51:21 (3372) [INFO]  One of the configured repositories failed (Unknown),[0m
[32m* 07-15:51:21 (3372) [INFO]  and yum doesn't have enough cached data to continue. At this point the only[0m
[32m* 07-15:51:21 (3372) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:[0m
[32m* 07-15:51:21 (3372) [INFO] [0m
[32m* 07-15:51:21 (3372) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.[0m
[32m* 07-15:51:21 (3372) [INFO] [0m
[32m* 07-15:51:21 (3372) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working[0m
[32m* 07-15:51:21 (3372) [INFO]         upstream. This is most often useful if you are using a newer[0m
[32m* 07-15:51:21 (3372) [INFO]         distribution release than is supported by the repository (and the[0m
[32m* 07-15:51:21 (3372) [INFO]         packages for the previous distribution release still work).[0m
[32m* 07-15:51:21 (3372) [INFO] [0m
[32m* 07-15:51:21 (3372) [INFO]      3. Run the command with the repository temporarily disabled[0m
[32m* 07-15:51:21 (3372) [INFO]             yum --disablerepo=<repoid> ...[0m
[32m* 07-15:51:21 (3372) [INFO] [0m
[32m* 07-15:51:21 (3372) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum[0m
[32m* 07-15:51:21 (3372) [INFO]         will then just ignore the repository until you permanently enable it[0m
[32m* 07-15:51:21 (3372) [INFO]         again or use --enablerepo for temporary usage:[0m
[32m* 07-15:51:21 (3372) [INFO] [0m
[32m* 07-15:51:21 (3372) [INFO]             yum-config-manager --disable <repoid>[0m
[32m* 07-15:51:21 (3372) [INFO]         or[0m
[32m* 07-15:51:21 (3372) [INFO]             subscription-manager repos --disable=<repoid>[0m
[32m* 07-15:51:21 (3372) [INFO] [0m
[32m* 07-15:51:21 (3372) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.[0m
[32m* 07-15:51:21 (3372) [INFO]         Note that yum will try to contact the repo. when it runs most commands,[0m
[32m* 07-15:51:21 (3372) [INFO]         so will have to try and fail each time (and thus. yum will be be much[0m
[32m* 07-15:51:21 (3372) [INFO]         slower). If it is a very temporary problem though, this is often a nice[0m
[32m* 07-15:51:21 (3372) [INFO]         compromise:[0m
[32m* 07-15:51:21 (3372) [INFO] [0m
[32m* 07-15:51:21 (3372) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true[0m
[32m* 07-15:51:21 (3372) [INFO] [0m
[32m* 07-15:51:21 (3372) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again[0m
[32m* 07-15:51:21 (3382) [INFO] [0m
[33m* 07-15:51:21 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 07-15:51:21 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 07-15:51:21 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 07-15:51:21 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[33m* 07-15:51:25 (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.
[0m
[33m* 07-15:51:25 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 08-02:17:17 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 08-02:17:17 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 08-02:17:17 (3362) [INFO] [0m
[32m* 08-02:17:17 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 08-02:17:17 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 08-02:17:17 (3372) [INFO]               : epel extras updates[0m
[32m* 08-02:17:17 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 08-02:17:18 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 08-02:17:18 (3382) [INFO] [0m
[32m* 08-02:17:18 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 08-02:17:18 (3362) [INFO] [0m
[32m* 08-02:17:18 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 08-02:17:18 (3372) [INFO] Determining fastest mirrors[0m
[32m* 08-02:17:23 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 08-02:17:23 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 08-02:17:23 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 08-02:17:23 (3372) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 08-02:17:23 (3372) [INFO]  * epel: mirror.ps.kz[0m
[32m* 08-02:17:23 (3372) [INFO]  * extras: mirror.natro.com[0m
[32m* 08-02:17:23 (3372) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 08-02:17:51 (3382) [INFO] [0m
[32m* 08-02:17:51 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 08-02:17:51 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 08-02:17:51 (3362) [INFO] [0m
[32m* 08-02:17:51 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 08-02:17:53 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 08-02:17:53 (3382) [INFO] [0m
[32m* 08-02:17:53 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 08-02:17:53 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 08-02:17:54 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-08_02:17:54_modified_for_AlmaLinux_8.json[0m
[33m* 08-02:17:54 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 08-02:17:56 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 09-02:18:24 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 09-02:18:24 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 09-02:18:24 (3362) [INFO] [0m
[32m* 09-02:18:24 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 09-02:18:24 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 09-02:18:24 (3372) [INFO]               : epel extras updates[0m
[32m* 09-02:18:25 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 09-02:18:25 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 09-02:18:25 (3382) [INFO] [0m
[32m* 09-02:18:25 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 09-02:18:25 (3362) [INFO] [0m
[32m* 09-02:18:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 09-02:18:25 (3372) [INFO] Determining fastest mirrors[0m
[32m* 09-02:18:30 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 09-02:18:30 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 09-02:18:30 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 09-02:18:30 (3372) [INFO]  * base: mirror.natro.com[0m
[32m* 09-02:18:30 (3372) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 09-02:18:30 (3372) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 09-02:18:30 (3372) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 09-02:19:04 (3372) [INFO] http://mirror.earthlink.iq/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 12] Timeout on http://mirror.earthlink.iq/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')[0m
[32m* 09-02:19:04 (3372) [INFO] Trying other mirror.[0m
[32m* 09-02:19:19 (3382) [INFO] [0m
[32m* 09-02:19:19 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 09-02:19:19 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 09-02:19:19 (3362) [INFO] [0m
[32m* 09-02:19:20 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 09-02:19:21 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 09-02:19:21 (3382) [INFO] [0m
[32m* 09-02:19:21 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 09-02:19:21 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 09-02:19:22 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-09_02:19:22_modified_for_AlmaLinux_8.json[0m
[33m* 09-02:19: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 09-02:19:23 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 10-02:16:25 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 10-02:16:25 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 10-02:16:25 (3362) [INFO] [0m
[32m* 10-02:16:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 10-02:16:25 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 10-02:16:25 (3372) [INFO]               : epel extras updates[0m
[32m* 10-02:16:25 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 10-02:16:25 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 10-02:16:25 (3382) [INFO] [0m
[32m* 10-02:16:25 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 10-02:16:25 (3362) [INFO] [0m
[32m* 10-02:16:26 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 10-02:16:26 (3372) [INFO] Determining fastest mirrors[0m
[32m* 10-02:16:31 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 10-02:16:31 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 10-02:16:31 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 10-02:16:31 (3372) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 10-02:16:31 (3372) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 10-02:16:31 (3372) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 10-02:16:31 (3372) [INFO]  * updates: mirror.natro.com[0m
[32m* 10-02:17:01 (3382) [INFO] [0m
[32m* 10-02:17:01 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 10-02:17:01 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 10-02:17:01 (3362) [INFO] [0m
[32m* 10-02:17:02 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 10-02:17:03 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 10-02:17:03 (3382) [INFO] [0m
[32m* 10-02:17:03 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 10-02:17:03 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 10-02:17:05 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-10_02:17:05_modified_for_AlmaLinux_8.json[0m
[33m* 10-02:17:05 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 10-02:17:07 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 11-02:22:34 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 11-02:22:34 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 11-02:22:34 (3362) [INFO] [0m
[32m* 11-02:22:34 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 11-02:22:34 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 11-02:22:34 (3372) [INFO]               : epel extras updates[0m
[32m* 11-02:22:34 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 11-02:22:34 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 11-02:22:34 (3382) [INFO] [0m
[32m* 11-02:22:34 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 11-02:22:34 (3362) [INFO] [0m
[32m* 11-02:22:35 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 11-02:22:35 (3372) [INFO] Determining fastest mirrors[0m
[32m* 11-02:22:40 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 11-02:22:40 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 11-02:22:40 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 11-02:22:40 (3372) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 11-02:22:40 (3372) [INFO]  * epel: mirror.ps.kz[0m
[32m* 11-02:22:40 (3372) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 11-02:22:40 (3372) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 11-02:23:02 (3382) [INFO] [0m
[32m* 11-02:23:02 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 11-02:23:02 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 11-02:23:02 (3362) [INFO] [0m
[32m* 11-02:23:02 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 11-02:23:03 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 11-02:23:03 (3382) [INFO] [0m
[32m* 11-02:23:03 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 11-02:23:03 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 11-02:23:04 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-11_02:23:04_modified_for_AlmaLinux_8.json[0m
[33m* 11-02:23:04 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 11-02:23:06 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 12-02:21:30 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 12-02:21:30 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 12-02:21:30 (3362) [INFO] [0m
[32m* 12-02:21:30 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 12-02:21:30 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 12-02:21:30 (3372) [INFO]               : epel extras updates[0m
[32m* 12-02:21:30 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 12-02:21:30 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 12-02:21:30 (3382) [INFO] [0m
[32m* 12-02:21:30 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 12-02:21:30 (3362) [INFO] [0m
[32m* 12-02:21:31 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 12-02:21:31 (3372) [INFO] Determining fastest mirrors[0m
[32m* 12-02:21:36 (3372) [INFO]  * EA4: 178.18.193.52[0m
[32m* 12-02:21:36 (3372) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 12-02:21:36 (3372) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 12-02:21:36 (3372) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 12-02:21:36 (3372) [INFO]  * epel: mirror.ps.kz[0m
[32m* 12-02:21:36 (3372) [INFO]  * extras: mirror.natro.com[0m
[32m* 12-02:21:36 (3372) [INFO]  * updates: mirror.natro.com[0m
[32m* 12-02:21:59 (3382) [INFO] [0m
[32m* 12-02:21:59 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 12-02:21:59 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 12-02:21:59 (3362) [INFO] [0m
[32m* 12-02:22:00 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 12-02:22:01 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 12-02:22:01 (3382) [INFO] [0m
[32m* 12-02:22:01 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 12-02:22:01 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 12-02:22:02 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-12_02:22:02_modified_for_AlmaLinux_8.json[0m
[33m* 12-02:22:02 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 12-02:22:03 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 13-02:29:50 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 13-02:29:50 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 13-02:29:50 (3362) [INFO] [0m
[32m* 13-02:29:50 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 13-02:29:50 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 13-02:29:50 (3372) [INFO]               : epel extras updates[0m
[32m* 13-02:29:50 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 13-02:29:50 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 13-02:29:50 (3382) [INFO] [0m
[32m* 13-02:29:50 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 13-02:29:50 (3362) [INFO] [0m
[32m* 13-02:29:51 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 13-02:29:51 (3372) [INFO] Determining fastest mirrors[0m
[32m* 13-02:29:55 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 13-02:29:55 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 13-02:29:55 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 13-02:29:55 (3372) [INFO]  * base: mirror.natro.com[0m
[32m* 13-02:29:55 (3372) [INFO]  * epel: mirror.alwyzon.net[0m
[32m* 13-02:29:55 (3372) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 13-02:29:55 (3372) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 13-02:30:20 (3382) [INFO] [0m
[32m* 13-02:30:20 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 13-02:30:20 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 13-02:30:20 (3362) [INFO] [0m
[32m* 13-02:30:20 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 13-02:30:22 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 13-02:30:22 (3382) [INFO] [0m
[32m* 13-02:30:22 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 13-02:30:22 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 13-02:30:24 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-13_02:30:24_modified_for_AlmaLinux_8.json[0m
[33m* 13-02:30:24 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 13-02:30:26 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 13-12:46:57 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 13-12:46:58 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 13-12:46:58 (3362) [INFO] [0m
[32m* 13-12:46:59 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 13-12:46:59 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 13-12:46:59 (3372) [INFO]               : epel extras updates[0m
[32m* 13-12:47:09 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 13-12:47:09 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 13-12:47:09 (3382) [INFO] [0m
[32m* 13-12:47:09 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 13-12:47:09 (3362) [INFO] [0m
[32m* 13-12:47:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 13-12:47:10 (3372) [INFO] Determining fastest mirrors[0m
[32m* 13-12:47:13 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 13-12:47:13 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 13-12:47:13 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 13-12:47:13 (3372) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 13-12:47:13 (3372) [INFO]  * epel: mirror.ps.kz[0m
[32m* 13-12:47:13 (3372) [INFO]  * extras: mirror.netdirekt.com.tr[0m
[32m* 13-12:47:13 (3372) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 13-12:47:36 (3382) [INFO] [0m
[32m* 13-12:47:36 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 13-12:47:36 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 13-12:47:36 (3362) [INFO] [0m
[32m* 13-12:47:36 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 13-12:47:38 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 13-12:47:38 (3382) [INFO] [0m
[32m* 13-12:47:38 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 13-12:47:38 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 13-12:47:39 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-13_12:47:39_modified_for_AlmaLinux_8.json[0m
[33m* 13-12: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 13-12:47:41 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 14-02:20:22 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 14-02:20:22 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 14-02:20:22 (3362) [INFO] [0m
[32m* 14-02:20:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 14-02:20:22 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 14-02:20:22 (3372) [INFO]               : epel extras updates[0m
[32m* 14-02:20:23 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 14-02:20:23 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 14-02:20:23 (3382) [INFO] [0m
[32m* 14-02:20:23 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 14-02:20:23 (3362) [INFO] [0m
[32m* 14-02:20:23 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 14-02:20:23 (3372) [INFO] Determining fastest mirrors[0m
[32m* 14-02:20:29 (3372) [INFO]  * EA4: 178.18.193.52[0m
[32m* 14-02:20:29 (3372) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 14-02:20:29 (3372) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 14-02:20:29 (3372) [INFO]  * base: mirror.netdirekt.com.tr[0m
[32m* 14-02:20:29 (3372) [INFO]  * epel: mirror.ps.kz[0m
[32m* 14-02:20:29 (3372) [INFO]  * extras: centos.vargonen.com[0m
[32m* 14-02:20:29 (3372) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 14-02:20:57 (3382) [INFO] [0m
[32m* 14-02:20:57 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 14-02:20:57 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 14-02:20:57 (3362) [INFO] [0m
[32m* 14-02:20:57 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 14-02:20:59 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 14-02:20:59 (3382) [INFO] [0m
[32m* 14-02:20:59 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 14-02:20:59 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 14-02:21:02 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-14_02:21:01_modified_for_AlmaLinux_8.json[0m
[33m* 14-02:21:02 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 14-02:21:03 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 14-15:58:17 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 14-15:58:17 (3077) [ERROR] https://repo.extreme-ix.org/epel/7/x86_64/repodata/6626423c0ee0560a872a3ff029a1b49e91cb0956d6921975a007ef965653039c-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/.

[0m
[33m* 14-15:58:17 (2504) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 14-15:58:18 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 14-15:58:18 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 14-15:58:18 (3362) [INFO] [0m
[32m* 14-15:58:18 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 14-15:58:18 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 14-15:58:18 (3372) [INFO]               : epel extras updates[0m
[32m* 14-15:58:19 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 14-15:58:19 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 14-15:58:19 (3382) [INFO] [0m
[32m* 14-15:58:19 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 14-15:58:19 (3362) [INFO] [0m
[32m* 14-15:58:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 14-15:58:19 (3372) [INFO] Determining fastest mirrors[0m
[32m* 14-15:58:24 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 14-15:58:24 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 14-15:58:24 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 14-15:58:24 (3372) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 14-15:58:24 (3372) [INFO]  * epel: mirror.ps.kz[0m
[32m* 14-15:58:24 (3372) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 14-15:58:24 (3372) [INFO]  * updates: mirror.netdirekt.com.tr[0m
[32m* 14-15:58:28 (3372) [INFO] https://repo.extreme-ix.org/epel/7/x86_64/repodata/691cb47bd594e2b8d64b316255d60dc0cf130d5cea1e9a49b8a95aa1a0464389-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found[0m
[32m* 14-15:58:28 (3372) [INFO] Trying other mirror.[0m
[32m* 14-15:58:28 (3372) [INFO] To address this issue please refer to the below wiki article [0m
[32m* 14-15:58:28 (3372) [INFO] [0m
[32m* 14-15:58:28 (3372) [INFO] https://wiki.centos.org/yum-errors[0m
[32m* 14-15:58:28 (3372) [INFO] [0m
[32m* 14-15:58:28 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.[0m
[32m* 14-15:58:28 (3372) [INFO] [0m
[32m* 14-15:58:46 (3382) [INFO] [0m
[32m* 14-15:58:46 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 14-15:58:46 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 14-15:58:46 (3362) [INFO] [0m
[32m* 14-15:58:47 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 14-15:58:48 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 14-15:58:48 (3382) [INFO] [0m
[32m* 14-15:58:48 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 14-15:58:48 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 14-15:58:49 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-14_15:58:49_modified_for_AlmaLinux_8.json[0m
[33m* 14-15:58: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 14-15:58:50 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 15-02:26:08 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 15-02:26:08 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 15-02:26:08 (3362) [INFO] [0m
[32m* 15-02:26:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 15-02:26:09 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 15-02:26:09 (3372) [INFO]               : epel extras updates[0m
[32m* 15-02:26:09 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 15-02:26:09 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 15-02:26:09 (3382) [INFO] [0m
[32m* 15-02:26:09 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 15-02:26:09 (3362) [INFO] [0m
[32m* 15-02:26:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 15-02:26:10 (3372) [INFO] Determining fastest mirrors[0m
[32m* 15-02:26:13 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 15-02:26:13 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 15-02:26:13 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 15-02:26:13 (3372) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 15-02:26:13 (3372) [INFO]  * epel: mirror.ps.kz[0m
[32m* 15-02:26:13 (3372) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 15-02:26:13 (3372) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 15-02:26:36 (3382) [INFO] [0m
[32m* 15-02:26:36 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 15-02:26:36 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 15-02:26:36 (3362) [INFO] [0m
[32m* 15-02:26:37 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 15-02:26:38 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 15-02:26:38 (3382) [INFO] [0m
[32m* 15-02:26:38 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 15-02:26:38 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 15-02:26:40 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-15_02:26:40_modified_for_AlmaLinux_8.json[0m
[33m* 15-02:26: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 15-02:26:41 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 16-02:26:13 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 16-02:26:13 (3077) [ERROR] https://repo.extreme-ix.org/epel/7/x86_64/repodata/209cf9a4ee3c35ddc3e75eb9b27f7b4aab85f49abac26d30d90ba1bd86ece1bd-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://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/209cf9a4ee3c35ddc3e75eb9b27f7b4aab85f49abac26d30d90ba1bd86ece1bd-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
[0m
[33m* 16-02:26:13 (2504) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 16-02:26:14 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 16-02:26:14 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 16-02:26:14 (3362) [INFO] [0m
[32m* 16-02:26:14 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 16-02:26:14 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 16-02:26:14 (3372) [INFO]               : epel extras updates[0m
[32m* 16-02:26:15 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 16-02:26:15 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 16-02:26:15 (3382) [INFO] [0m
[32m* 16-02:26:15 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 16-02:26:15 (3362) [INFO] [0m
[32m* 16-02:26:16 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 16-02:26:16 (3372) [INFO] Determining fastest mirrors[0m
[32m* 16-02:26:23 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 16-02:26:23 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 16-02:26:23 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 16-02:26:23 (3372) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 16-02:26:23 (3372) [INFO]  * epel: mirror.ps.kz[0m
[32m* 16-02:26:23 (3372) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 16-02:26:23 (3372) [INFO]  * updates: mirror.netdirekt.com.tr[0m
[32m* 16-02:26:28 (3372) [INFO] http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/bed619d983b761c12c7a0ed451887d68412fd84af22957300e7a88a1f09bf928-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found[0m
[32m* 16-02:26:28 (3372) [INFO] Trying other mirror.[0m
[32m* 16-02:26:28 (3372) [INFO] To address this issue please refer to the below wiki article [0m
[32m* 16-02:26:28 (3372) [INFO] [0m
[32m* 16-02:26:28 (3372) [INFO] https://wiki.centos.org/yum-errors[0m
[32m* 16-02:26:28 (3372) [INFO] [0m
[32m* 16-02:26:28 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.[0m
[32m* 16-02:26:28 (3372) [INFO] [0m
[32m* 16-02:26:28 (3372) [INFO] https://repo.extreme-ix.org/epel/7/x86_64/repodata/47e230566f114075d86b1d5c6d43c914bd2f853ecc1a0ff806030014b5b601a9-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found[0m
[32m* 16-02:26:28 (3372) [INFO] Trying other mirror.[0m
[32m* 16-02:26:29 (3372) [INFO] http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/47e230566f114075d86b1d5c6d43c914bd2f853ecc1a0ff806030014b5b601a9-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found[0m
[32m* 16-02:26:29 (3372) [INFO] Trying other mirror.[0m
[32m* 16-02:26:29 (3372) [INFO] https://mirror.sabay.com.kh/epel/7/x86_64/repodata/bed619d983b761c12c7a0ed451887d68412fd84af22957300e7a88a1f09bf928-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found[0m
[32m* 16-02:26:29 (3372) [INFO] Trying other mirror.[0m
[32m* 16-02:26:30 (3372) [INFO] https://repo.extreme-ix.org/epel/7/x86_64/repodata/bed619d983b761c12c7a0ed451887d68412fd84af22957300e7a88a1f09bf928-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found[0m
[32m* 16-02:26:30 (3372) [INFO] Trying other mirror.[0m
[32m* 16-02:26:48 (3382) [INFO] [0m
[32m* 16-02:26:48 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 16-02:26:48 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 16-02:26:48 (3362) [INFO] [0m
[32m* 16-02:26:49 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 16-02:26:51 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 16-02:26:51 (3382) [INFO] [0m
[32m* 16-02:26:51 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 16-02:26:51 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 16-02:26:56 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-16_02:26:56_modified_for_AlmaLinux_8.json[0m
[33m* 16-02:26:56 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 16-02:26:59 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 17-02:27:59 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 17-02:27:59 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 17-02:27:59 (3362) [INFO] [0m
[32m* 17-02:28:00 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 17-02:28:00 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 17-02:28:00 (3372) [INFO]               : epel extras updates[0m
[32m* 17-02:28:00 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 17-02:28:00 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 17-02:28:00 (3382) [INFO] [0m
[32m* 17-02:28:00 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 17-02:28:00 (3362) [INFO] [0m
[32m* 17-02:28:00 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 17-02:28:01 (3372) [INFO] Determining fastest mirrors[0m
[32m* 17-02:28:06 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 17-02:28:06 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 17-02:28:06 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 17-02:28:06 (3372) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 17-02:28:06 (3372) [INFO]  * epel: mirror.ps.kz[0m
[32m* 17-02:28:06 (3372) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 17-02:28:06 (3372) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 17-02:28:40 (3382) [INFO] [0m
[32m* 17-02:28:40 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 17-02:28:40 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 17-02:28:40 (3362) [INFO] [0m
[32m* 17-02:28:42 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 17-02:29:06 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 17-02:29:06 (3382) [INFO] [0m
[32m* 17-02:29:06 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 17-02:29:06 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 17-02:29:09 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-17_02:29:09_modified_for_AlmaLinux_8.json[0m
[33m* 17-02:29:09 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 17-02:29:12 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 18-02:24:09 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 18-02:24:09 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 18-02:24:09 (3362) [INFO] [0m
[32m* 18-02:24:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 18-02:24:09 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 18-02:24:09 (3372) [INFO]               : epel extras updates[0m
[32m* 18-02:24:09 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 18-02:24:09 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 18-02:24:09 (3382) [INFO] [0m
[32m* 18-02:24:09 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 18-02:24:09 (3362) [INFO] [0m
[32m* 18-02:24:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 18-02:24:10 (3372) [INFO] Determining fastest mirrors[0m
[32m* 18-02:24:14 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 18-02:24:14 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 18-02:24:14 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 18-02:24:14 (3372) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 18-02:24:14 (3372) [INFO]  * epel: mirror.yer.az[0m
[32m* 18-02:24:14 (3372) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 18-02:24:14 (3372) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 18-02:24:52 (3382) [INFO] [0m
[32m* 18-02:24:52 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 18-02:24:52 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 18-02:24:52 (3362) [INFO] [0m
[32m* 18-02:24:53 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 18-02:24:54 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 18-02:24:54 (3382) [INFO] [0m
[32m* 18-02:24:54 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 18-02:24:54 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 18-02:24:55 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-18_02:24:55_modified_for_AlmaLinux_8.json[0m
[33m* 18-02:24:55 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

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

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


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

[0m
[33m* 18-02:24:57 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 19-02:17:09 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 19-02:17:10 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 19-02:17:10 (3362) [INFO] [0m
[32m* 19-02:17:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 19-02:17:10 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 19-02:17:10 (3372) [INFO]               : epel extras updates[0m
[32m* 19-02:17:10 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 19-02:17:10 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 19-02:17:10 (3382) [INFO] [0m
[32m* 19-02:17:10 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 19-02:17:10 (3362) [INFO] [0m
[32m* 19-02:17:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 19-02:17:11 (3372) [INFO] Determining fastest mirrors[0m
[32m* 19-02:17:15 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 19-02:17:15 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 19-02:17:15 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 19-02:17:15 (3372) [INFO]  * base: mirror.netdirekt.com.tr[0m
[32m* 19-02:17:15 (3372) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 19-02:17:15 (3372) [INFO]  * extras: mirror.netdirekt.com.tr[0m
[32m* 19-02:17:15 (3372) [INFO]  * updates: mirror.netdirekt.com.tr[0m
[32m* 19-02:17:51 (3382) [INFO] [0m
[32m* 19-02:17:51 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 19-02:17:51 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 19-02:17:51 (3362) [INFO] [0m
[32m* 19-02:17:51 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 19-02:17:53 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 19-02:17:53 (3382) [INFO] [0m
[32m* 19-02:17:53 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 19-02:17:53 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 19-02:17:54 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-19_02:17:54_modified_for_AlmaLinux_8.json[0m
[33m* 19-02:17:54 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 19-02:17:55 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

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


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

[0m
[33m* 19-02:17:55 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 20-02:35:02 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 20-02:35:02 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 20-02:35:02 (3362) [INFO] [0m
[32m* 20-02:35:03 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 20-02:35:03 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 20-02:35:03 (3372) [INFO]               : epel extras updates[0m
[32m* 20-02:35:03 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 20-02:35:03 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 20-02:35:03 (3382) [INFO] [0m
[32m* 20-02:35:03 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 20-02:35:03 (3362) [INFO] [0m
[32m* 20-02:35:03 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 20-02:35:04 (3372) [INFO] Determining fastest mirrors[0m
[32m* 20-02:35:36 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 20-02:35:36 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 20-02:35:36 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 20-02:35:36 (3372) [INFO]  * base: mirror.netdirekt.com.tr[0m
[32m* 20-02:35:36 (3372) [INFO]  * epel: mirror.yer.az[0m
[32m* 20-02:35:36 (3372) [INFO]  * extras: ftp.linux.org.tr[0m
[32m* 20-02:35:36 (3372) [INFO]  * updates: mirror.netdirekt.com.tr[0m
[32m* 20-02:36:34 (3382) [INFO] [0m
[32m* 20-02:36:34 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 20-02:36:34 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 20-02:36:34 (3362) [INFO] [0m
[32m* 20-02:36:35 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 20-02:36:37 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 20-02:36:37 (3382) [INFO] [0m
[32m* 20-02:36:37 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 20-02:36:37 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 20-02:36:39 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-20_02:36:39_modified_for_AlmaLinux_8.json[0m
[33m* 20-02:36: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 20-02:36:46 (2504) [WARN] *** Elevation Blocker detected: ***
This script does not appear to be the newest available release.
Please download the latest version from the following URL and try again:

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


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

[0m
[33m* 20-02:36:46 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 21-15:52:14 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 21-15:52:14 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 21-15:52:14 (3362) [INFO] [0m
[32m* 21-15:52:14 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 21-15:52:15 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 21-15:52:15 (3372) [INFO]               : epel extras updates[0m
[32m* 21-15:52:15 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 21-15:52:15 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 21-15:52:15 (3382) [INFO] [0m
[32m* 21-15:52:15 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 21-15:52:15 (3362) [INFO] [0m
[32m* 21-15:52:15 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 21-15:52:16 (3372) [INFO] Determining fastest mirrors[0m
[32m* 21-15:52:21 (3372) [INFO]  * EA4: 178.18.193.52[0m
[32m* 21-15:52:21 (3372) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 21-15:52:21 (3372) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 21-15:52:21 (3372) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 21-15:52:21 (3372) [INFO]  * epel: mirror.yer.az[0m
[32m* 21-15:52:21 (3372) [INFO]  * extras: ftp.linux.org.tr[0m
[32m* 21-15:52:21 (3372) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 21-15:53:55 (3382) [INFO] [0m
[32m* 21-15:53:55 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 21-15:53:55 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 21-15:53:55 (3362) [INFO] [0m
[32m* 21-15:53:55 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 21-15:53:56 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 21-15:53:56 (3382) [INFO] [0m
[32m* 21-15:53:56 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 21-15:53:56 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 21-15:53:57 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-21_15:53:57_modified_for_AlmaLinux_8.json[0m
[33m* 21-15:53:57 (2504) [WARN] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

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

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


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

[0m
[33m* 21-15:53:58 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 22-02:18:54 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 22-02:18:54 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 22-02:18:54 (3362) [INFO] [0m
[32m* 22-02:18:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 22-02:18:55 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 22-02:18:55 (3372) [INFO]               : epel extras updates[0m
[32m* 22-02:18:55 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 22-02:18:55 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 22-02:18:55 (3382) [INFO] [0m
[32m* 22-02:18:55 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 22-02:18:55 (3362) [INFO] [0m
[32m* 22-02:18:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 22-02:18:56 (3372) [INFO] Determining fastest mirrors[0m
[32m* 22-02:19:09 (3372) [INFO]  * EA4: 93.115.203.100[0m
[32m* 22-02:19:09 (3372) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 22-02:19:09 (3372) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 22-02:19:09 (3372) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 22-02:19:09 (3372) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 22-02:19:09 (3372) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 22-02:19:09 (3372) [INFO]  * updates: mirror.netdirekt.com.tr[0m
[32m* 22-02:19:32 (3382) [INFO] [0m
[32m* 22-02:19:32 (2932) [INFO] Checking /scripts/sysup[0m
[32m* 22-02:19:32 (3361) [INFO] Running: /scripts/sysup[0m
[32m* 22-02:19:32 (3362) [INFO] [0m
[32m* 22-02:19:33 (3372) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 22-02:19:34 (3372) [INFO]   All Needed Packages are already installed.[0m
[32m* 22-02:19:34 (3382) [INFO] [0m
[32m* 22-02:19:34 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 22-02:19:35 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 22-02:19:39 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-22_02:19:39_modified_for_AlmaLinux_8.json[0m
[33m* 22-02:19: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 22-02:19: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.

[0m
[33m* 22-02:19:40 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 23-02:21:37 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 23-02:21:38 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 23-02:21:38 (3362) [INFO] [0m
[32m* 23-02:21:38 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 23-02:21:38 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 23-02:21:38 (3372) [INFO]               : epel extras updates[0m
[32m* 23-02:21:38 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 23-02:21:38 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 23-02:21:38 (3382) [INFO] [0m
[32m* 23-02:21:38 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 23-02:21:38 (3362) [INFO] [0m
[32m* 23-02:21:39 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 23-02:21:39 (3372) [INFO] Determining fastest mirrors[0m
[32m* 23-02:22:14 (3372) [INFO] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was[0m
[32m* 23-02:22:14 (3372) [INFO] 12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Resolving timed out after 30590 milliseconds')[0m
[32m* 23-02:22:14 (3372) [INFO] [0m
[32m* 23-02:22:14 (3372) [INFO] [0m
[32m* 23-02:22:14 (3372) [INFO]  One of the configured repositories failed (Unknown),[0m
[32m* 23-02:22:14 (3372) [INFO]  and yum doesn't have enough cached data to continue. At this point the only[0m
[32m* 23-02:22:14 (3372) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:[0m
[32m* 23-02:22:14 (3372) [INFO] [0m
[32m* 23-02:22:14 (3372) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.[0m
[32m* 23-02:22:14 (3372) [INFO] [0m
[32m* 23-02:22:14 (3372) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working[0m
[32m* 23-02:22:14 (3372) [INFO]         upstream. This is most often useful if you are using a newer[0m
[32m* 23-02:22:14 (3372) [INFO]         distribution release than is supported by the repository (and the[0m
[32m* 23-02:22:14 (3372) [INFO]         packages for the previous distribution release still work).[0m
[32m* 23-02:22:14 (3372) [INFO] [0m
[32m* 23-02:22:14 (3372) [INFO]      3. Run the command with the repository temporarily disabled[0m
[32m* 23-02:22:14 (3372) [INFO]             yum --disablerepo=<repoid> ...[0m
[32m* 23-02:22:14 (3372) [INFO] [0m
[32m* 23-02:22:14 (3372) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum[0m
[32m* 23-02:22:14 (3372) [INFO]         will then just ignore the repository until you permanently enable it[0m
[32m* 23-02:22:14 (3372) [INFO]         again or use --enablerepo for temporary usage:[0m
[32m* 23-02:22:14 (3372) [INFO] [0m
[32m* 23-02:22:14 (3372) [INFO]             yum-config-manager --disable <repoid>[0m
[32m* 23-02:22:14 (3372) [INFO]         or[0m
[32m* 23-02:22:14 (3372) [INFO]             subscription-manager repos --disable=<repoid>[0m
[32m* 23-02:22:14 (3372) [INFO] [0m
[32m* 23-02:22:14 (3372) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.[0m
[32m* 23-02:22:14 (3372) [INFO]         Note that yum will try to contact the repo. when it runs most commands,[0m
[32m* 23-02:22:14 (3372) [INFO]         so will have to try and fail each time (and thus. yum will be be much[0m
[32m* 23-02:22:14 (3372) [INFO]         slower). If it is a very temporary problem though, this is often a nice[0m
[32m* 23-02:22:14 (3372) [INFO]         compromise:[0m
[32m* 23-02:22:14 (3372) [INFO] [0m
[32m* 23-02:22:14 (3372) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true[0m
[32m* 23-02:22:14 (3372) [INFO] [0m
[32m* 23-02:22:14 (3372) [INFO] Cannot find a valid baseurl for repo: EA4/7/x86_64[0m
[32m* 23-02:22:14 (3382) [INFO] [0m
[33m* 23-02:22:14 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 23-02:22:14 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 23-02:22:14 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 23-02:22:14 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[32m* 23-02:22:38 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-23_02:22:38_modified_for_AlmaLinux_8.json[0m
[33m* 23-02:22: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 23-02:22: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.

[0m
[33m* 23-02:22:40 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 24-02:19:39 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 24-02:19:39 (3077) [ERROR] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
[0m
[33m* 24-02:19:39 (2504) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 24-02:19:40 (2925) [INFO] Checking if your system is up to date: [0m
[32m* 24-02:19:40 (3361) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 24-02:19:40 (3362) [INFO] [0m
[32m* 24-02:19:40 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 24-02:19:40 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 24-02:19:40 (3372) [INFO]               : epel extras updates[0m
[32m* 24-02:19:40 (3372) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 24-02:19:40 (3372) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 24-02:19:40 (3382) [INFO] [0m
[32m* 24-02:19:40 (3361) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 24-02:19:40 (3362) [INFO] [0m
[32m* 24-02:19:41 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 24-02:19:41 (3372) [INFO] Determining fastest mirrors[0m
[32m* 24-02:20:13 (3372) [INFO] [0m
[32m* 24-02:20:13 (3372) [INFO] [0m
[32m* 24-02:20:13 (3372) [INFO]  One of the configured repositories failed (Unknown),[0m
[32m* 24-02:20:13 (3372) [INFO]  and yum doesn't have enough cached data to continue. At this point the only[0m
[32m* 24-02:20:13 (3372) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:[0m
[32m* 24-02:20:13 (3372) [INFO] [0m
[32m* 24-02:20:13 (3372) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.[0m
[32m* 24-02:20:13 (3372) [INFO] [0m
[32m* 24-02:20:13 (3372) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working[0m
[32m* 24-02:20:13 (3372) [INFO]         upstream. This is most often useful if you are using a newer[0m
[32m* 24-02:20:13 (3372) [INFO]         distribution release than is supported by the repository (and the[0m
[32m* 24-02:20:13 (3372) [INFO]         packages for the previous distribution release still work).[0m
[32m* 24-02:20:13 (3372) [INFO] [0m
[32m* 24-02:20:13 (3372) [INFO]      3. Run the command with the repository temporarily disabled[0m
[32m* 24-02:20:13 (3372) [INFO]             yum --disablerepo=<repoid> ...[0m
[32m* 24-02:20:13 (3372) [INFO] [0m
[32m* 24-02:20:13 (3372) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum[0m
[32m* 24-02:20:13 (3372) [INFO]         will then just ignore the repository until you permanently enable it[0m
[32m* 24-02:20:13 (3372) [INFO]         again or use --enablerepo for temporary usage:[0m
[32m* 24-02:20:13 (3372) [INFO] [0m
[32m* 24-02:20:13 (3372) [INFO]             yum-config-manager --disable <repoid>[0m
[32m* 24-02:20:13 (3372) [INFO]         or[0m
[32m* 24-02:20:13 (3372) [INFO]             subscription-manager repos --disable=<repoid>[0m
[32m* 24-02:20:13 (3372) [INFO] [0m
[32m* 24-02:20:13 (3372) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.[0m
[32m* 24-02:20:13 (3372) [INFO]         Note that yum will try to contact the repo. when it runs most commands,[0m
[32m* 24-02:20:13 (3372) [INFO]         so will have to try and fail each time (and thus. yum will be be much[0m
[32m* 24-02:20:13 (3372) [INFO]         slower). If it is a very temporary problem though, this is often a nice[0m
[32m* 24-02:20:13 (3372) [INFO]         compromise:[0m
[32m* 24-02:20:13 (3372) [INFO] [0m
[32m* 24-02:20:13 (3372) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true[0m
[32m* 24-02:20:13 (3372) [INFO] [0m
[32m* 24-02:20:13 (3372) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again[0m
[32m* 24-02:20:15 (3382) [INFO] [0m
[33m* 24-02:20:15 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 24-02:20:15 (2504) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 24-02:20:15 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8.[0m
[32m* 24-02:20:15 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8[0m
[33m* 24-02:20:51 (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.
[0m
[33m* 24-02:20:51 (570) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 24-02:21:48 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 24-02:21:48 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 24-02:21:48 (3767) [INFO] [0m
[32m* 24-02:21:49 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 24-02:21:49 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 24-02:21:49 (3777) [INFO]               : epel extras updates[0m
[32m* 24-02:21:50 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 24-02:21:50 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 24-02:21:50 (3787) [INFO] [0m
[32m* 24-02:21:50 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 24-02:21:50 (3767) [INFO] [0m
[32m* 24-02:21:50 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 24-02:21:51 (3777) [INFO] Determining fastest mirrors[0m
[32m* 24-02:21:58 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 24-02:21:58 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 24-02:21:58 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 24-02:21:58 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 24-02:21:58 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 24-02:21:58 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 24-02:21:58 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 24-02:22:24 (3787) [INFO] [0m
[32m* 24-02:22:24 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 24-02:22:24 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 24-02:22:24 (3767) [INFO] [0m
[32m* 24-02:22:25 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 24-02:22:27 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 24-02:22:27 (3787) [INFO] [0m
[32m* 24-02:22:27 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 24-02:22:27 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jBbV5jhJBl/ea_profile.json[0m
[32m* 24-02:22:28 (1619) [INFO] Backed up EA4 profile to /tmp/jBbV5jhJBl/ea_profile.json[0m
[33m* 24-02:22:28 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 24-02:22: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.

[0m
[33m* 24-02:22:29 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 26-02:32:10 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 26-02:32:10 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 26-02:32:10 (3767) [INFO] [0m
[32m* 26-02:32:10 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 26-02:32:11 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 26-02:32:11 (3777) [INFO]               : epel extras updates[0m
[32m* 26-02:32:11 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 26-02:32:11 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 26-02:32:11 (3787) [INFO] [0m
[32m* 26-02:32:11 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 26-02:32:11 (3767) [INFO] [0m
[32m* 26-02:32:11 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 26-02:32:11 (3777) [INFO] Determining fastest mirrors[0m
[32m* 26-02:32:24 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 26-02:32:24 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 26-02:32:24 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 26-02:32:24 (3777) [INFO]  * base: mirror.ni.net.tr[0m
[32m* 26-02:32:24 (3777) [INFO]  * epel: epel.mirror.angkasa.id[0m
[32m* 26-02:32:24 (3777) [INFO]  * extras: mirror.verinomi.com[0m
[32m* 26-02:32:24 (3777) [INFO]  * updates: centos.vargonen.com[0m
[32m* 26-02:32:52 (3787) [INFO] [0m
[32m* 26-02:32:52 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 26-02:32:52 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 26-02:32:52 (3767) [INFO] [0m
[32m* 26-02:32:52 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 26-02:32:53 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 26-02:32:53 (3787) [INFO] [0m
[32m* 26-02:32:53 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 26-02:32:53 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qHL6d6iA9n/ea_profile.json[0m
[32m* 26-02:32:55 (1619) [INFO] Backed up EA4 profile to /tmp/qHL6d6iA9n/ea_profile.json[0m
[33m* 26-02:32: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 26-02:32:56 (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.

[0m
[33m* 26-02:32:56 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 27-02:35:20 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 27-02:35:20 (3473) [ERROR] http://mirror.earthlink.iq/epel/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://mirror.earthlink.iq/epel/7/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror.ps.kz/epel/7/x86_64/repodata/b8ea4e241b35a34abf75b078c2b421525116231e89a015d150e98ece9ba6324f-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.ps.kz/epel/7/x86_64/repodata/2a347cd13737bf1e02be044ef0a2c72948a91b857b05574922fe78748357c813-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
[0m
[33m* 27-02:35:20 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 27-02:35:20 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 27-02:35:20 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 27-02:35:20 (3767) [INFO] [0m
[32m* 27-02:35:21 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 27-02:35:21 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 27-02:35:21 (3777) [INFO]               : epel extras updates[0m
[32m* 27-02:35:21 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 27-02:35:21 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 27-02:35:21 (3787) [INFO] [0m
[32m* 27-02:35:21 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 27-02:35:21 (3767) [INFO] [0m
[32m* 27-02:35:21 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 27-02:35:22 (3777) [INFO] Determining fastest mirrors[0m
[32m* 27-02:35:27 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 27-02:35:27 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 27-02:35:27 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 27-02:35:27 (3777) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 27-02:35:27 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 27-02:35:27 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 27-02:35:27 (3777) [INFO]  * updates: ftp.linux.org.tr[0m
[32m* 27-02:35:29 (3777) [INFO] http://mirror.earthlink.iq/epel/7/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 500 - Internal Server Error[0m
[32m* 27-02:35:29 (3777) [INFO] Trying other mirror.[0m
[32m* 27-02:35:44 (3777) [INFO] https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2401:1a80:0:100::20: Network is unreachable"[0m
[32m* 27-02:35:44 (3777) [INFO] Trying other mirror.[0m
[32m* 27-02:35:49 (3777) [INFO] http://mirror.earthlink.iq/epel/7/x86_64/repodata/f4f0bc70b879c0681f4332f311d763205defdc84a4a71ce139fb17b2cc7c4775-updateinfo.xml.bz2: [Errno 14] HTTP Error 500 - Internal Server Error[0m
[32m* 27-02:35:49 (3777) [INFO] Trying other mirror.[0m
[32m* 27-02:36:01 (3777) [INFO] https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/2bb955ce9784fadbd0d5d307896acb703ae49ffc26f56f887e074f92ef89da5e-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found[0m
[32m* 27-02:36:01 (3777) [INFO] Trying other mirror.[0m
[32m* 27-02:36:01 (3777) [INFO] To address this issue please refer to the below wiki article [0m
[32m* 27-02:36:01 (3777) [INFO] [0m
[32m* 27-02:36:01 (3777) [INFO] https://wiki.centos.org/yum-errors[0m
[32m* 27-02:36:01 (3777) [INFO] [0m
[32m* 27-02:36:01 (3777) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.[0m
[32m* 27-02:36:01 (3777) [INFO] [0m
[32m* 27-02:36:19 (3777) [INFO] https://linux.domainesia.com/fedora/fedora-epel/7/x86_64/repodata/f4f0bc70b879c0681f4332f311d763205defdc84a4a71ce139fb17b2cc7c4775-updateinfo.xml.bz2: [Errno 12] Timeout on https://linux.domainesia.com/fedora/fedora-epel/7/x86_64/repodata/f4f0bc70b879c0681f4332f311d763205defdc84a4a71ce139fb17b2cc7c4775-updateinfo.xml.bz2: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')[0m
[32m* 27-02:36:19 (3777) [INFO] Trying other mirror.[0m
[32m* 27-02:36:34 (3777) [INFO] https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/f4f0bc70b879c0681f4332f311d763205defdc84a4a71ce139fb17b2cc7c4775-updateinfo.xml.bz2: [Errno 14] curl#7 - "Failed to connect to 2401:1a80:0:100::20: Network is unreachable"[0m
[32m* 27-02:36:34 (3777) [INFO] Trying other mirror.[0m
[32m* 27-02:37:54 (3787) [INFO] [0m
[32m* 27-02:37:54 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 27-02:37:54 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 27-02:37:54 (3767) [INFO] [0m
[32m* 27-02:37:54 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 27-02:37:55 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 27-02:37:55 (3787) [INFO] [0m
[32m* 27-02:37:55 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 27-02:37:55 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Wc5bvx04Bk/ea_profile.json[0m
[32m* 27-02:37:56 (1619) [INFO] Backed up EA4 profile to /tmp/Wc5bvx04Bk/ea_profile.json[0m
[33m* 27-02:37: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 27-02:37: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.

[0m
[33m* 27-02:37:57 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 28-02:17:46 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 28-02:17:46 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 28-02:17:46 (3767) [INFO] [0m
[32m* 28-02:17:46 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 28-02:17:46 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 28-02:17:46 (3777) [INFO]               : epel extras updates[0m
[32m* 28-02:17:46 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 28-02:17:46 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 28-02:17:46 (3787) [INFO] [0m
[32m* 28-02:17:46 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 28-02:17:46 (3767) [INFO] [0m
[32m* 28-02:17:47 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 28-02:17:47 (3777) [INFO] Determining fastest mirrors[0m
[32m* 28-02:17:52 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 28-02:17:52 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 28-02:17:52 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 28-02:17:52 (3777) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 28-02:17:52 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 28-02:17:52 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 28-02:17:52 (3777) [INFO]  * updates: mirror.netdirekt.com.tr[0m
[32m* 28-02:18:13 (3787) [INFO] [0m
[32m* 28-02:18:13 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 28-02:18:13 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 28-02:18:13 (3767) [INFO] [0m
[32m* 28-02:18:13 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 28-02:18:14 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 28-02:18:14 (3787) [INFO] [0m
[32m* 28-02:18:14 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 28-02:18:14 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WRBObtAQef/ea_profile.json[0m
[32m* 28-02:18:16 (1619) [INFO] Backed up EA4 profile to /tmp/WRBObtAQef/ea_profile.json[0m
[33m* 28-02:18: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 28-02:18: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.

[0m
[33m* 28-02:18:17 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 28-15:53:57 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 28-15:53:57 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 28-15:53:57 (3767) [INFO] [0m
[32m* 28-15:53:57 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 28-15:53:58 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 28-15:53:58 (3777) [INFO]               : epel extras updates[0m
[32m* 28-15:53:58 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 28-15:53:58 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 28-15:53:58 (3787) [INFO] [0m
[32m* 28-15:53:58 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 28-15:53:58 (3767) [INFO] [0m
[32m* 28-15:53:58 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 28-15:53:59 (3777) [INFO] Determining fastest mirrors[0m
[32m* 28-15:54:05 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 28-15:54:05 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 28-15:54:05 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 28-15:54:05 (3777) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 28-15:54:05 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 28-15:54:05 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 28-15:54:05 (3777) [INFO]  * updates: centos.vargonen.com[0m
[32m* 28-15:54:28 (3787) [INFO] [0m
[32m* 28-15:54:28 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 28-15:54:28 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 28-15:54:28 (3767) [INFO] [0m
[32m* 28-15:54:29 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 28-15:54:30 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 28-15:54:30 (3787) [INFO] [0m
[32m* 28-15:54:30 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 28-15:54:30 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pg_dLIXVUs/ea_profile.json[0m
[32m* 28-15:54:31 (1619) [INFO] Backed up EA4 profile to /tmp/pg_dLIXVUs/ea_profile.json[0m
[33m* 28-15:54:31 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 28-15:54:32 (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.

[0m
[33m* 28-15:54:32 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 29-02:22:14 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 29-02:22:14 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 29-02:22:14 (3767) [INFO] [0m
[32m* 29-02:22:14 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 29-02:22:15 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 29-02:22:15 (3777) [INFO]               : epel extras updates[0m
[32m* 29-02:22:15 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 29-02:22:15 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 29-02:22:15 (3787) [INFO] [0m
[32m* 29-02:22:15 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 29-02:22:15 (3767) [INFO] [0m
[32m* 29-02:22:15 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 29-02:22:16 (3777) [INFO] Determining fastest mirrors[0m
[32m* 29-02:22:36 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 29-02:22:36 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 29-02:22:36 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 29-02:22:36 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 29-02:22:36 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 29-02:22:36 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 29-02:22:36 (3777) [INFO]  * updates: mirror.netdirekt.com.tr[0m
[32m* 29-02:22:56 (3777) [INFO] http://mirror.dimensi.cloud/epel/7/x86_64/repodata/7a3f19ebfed85c50b5e56547b100d62df97e42c68c7200fda1a4e0eaaf6543d2-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2401:1700:1c:f008:112:78:36:34: Network is unreachable"[0m
[32m* 29-02:22:56 (3777) [INFO] Trying other mirror.[0m
[32m* 29-02:23:14 (3787) [INFO] [0m
[32m* 29-02:23:14 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 29-02:23:14 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 29-02:23:14 (3767) [INFO] [0m
[32m* 29-02:23:15 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 29-02:23:17 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 29-02:23:17 (3787) [INFO] [0m
[32m* 29-02:23:17 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 29-02:23:17 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TUX33Cl6Wz/ea_profile.json[0m
[32m* 29-02:23:18 (1619) [INFO] Backed up EA4 profile to /tmp/TUX33Cl6Wz/ea_profile.json[0m
[33m* 29-02:23: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 29-02:23: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.

[0m
[33m* 29-02:23:19 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 30-02:27:21 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 30-02:27:21 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 30-02:27:21 (3767) [INFO] [0m
[32m* 30-02:27:24 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 30-02:27:24 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 30-02:27:24 (3777) [INFO]               : epel extras updates[0m
[32m* 30-02:27:25 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 30-02:27:25 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 30-02:27:25 (3787) [INFO] [0m
[32m* 30-02:27:25 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 30-02:27:25 (3767) [INFO] [0m
[32m* 30-02:27:30 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 30-02:27:59 (3777) [INFO] Determining fastest mirrors[0m
[32m* 30-02:28:14 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 30-02:28:14 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 30-02:28:14 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 30-02:28:14 (3777) [INFO]  * base: mirror.onlinehosting.com.tr[0m
[32m* 30-02:28:14 (3777) [INFO]  * epel: mirrors.bfsu.edu.cn[0m
[32m* 30-02:28:14 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 30-02:28:14 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 30-02:29:00 (3787) [INFO] [0m
[33m* 30-02:29:00 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 30-02:29:00 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 30-02:29:00 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 30-02:29:00 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/O6j1EBjgAS/ea_profile.json[0m
[32m* 30-02:29:08 (1619) [INFO] Backed up EA4 profile to /tmp/O6j1EBjgAS/ea_profile.json[0m
[33m* 30-02:29:08 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 30-02:29:09 (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.

[0m
[33m* 30-02:29:09 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 01-02:20:46 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 01-02:20:46 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 01-02:20:46 (3767) [INFO] [0m
[32m* 01-02:20:47 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 01-02:20:47 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 01-02:20:47 (3777) [INFO]               : epel extras updates[0m
[32m* 01-02:20:47 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 01-02:20:47 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 01-02:20:47 (3787) [INFO] [0m
[32m* 01-02:20:47 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 01-02:20:47 (3767) [INFO] [0m
[32m* 01-02:20:47 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 01-02:20:48 (3777) [INFO] Determining fastest mirrors[0m
[32m* 01-02:20:55 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 01-02:20:55 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 01-02:20:55 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 01-02:20:55 (3777) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 01-02:20:55 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 01-02:20:55 (3777) [INFO]  * extras: ftp.linux.org.tr[0m
[32m* 01-02:20:55 (3777) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 01-02:21:21 (3787) [INFO] [0m
[32m* 01-02:21:21 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 01-02:21:21 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 01-02:21:21 (3767) [INFO] [0m
[32m* 01-02:21:21 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 01-02:21:22 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 01-02:21:22 (3787) [INFO] [0m
[32m* 01-02:21:22 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 01-02:21:22 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/66D1XCKURK/ea_profile.json[0m
[32m* 01-02:21:25 (1619) [INFO] Backed up EA4 profile to /tmp/66D1XCKURK/ea_profile.json[0m
[33m* 01-02:21:25 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 01-02:21: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.

[0m
[33m* 01-02:21:27 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 02-02:19:38 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 02-02:19:38 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 02-02:19:38 (3767) [INFO] [0m
[32m* 02-02:19:39 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 02-02:19:39 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 02-02:19:39 (3777) [INFO]               : epel extras updates[0m
[32m* 02-02:19:39 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 02-02:19:39 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 02-02:19:39 (3787) [INFO] [0m
[32m* 02-02:19:39 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 02-02:19:39 (3767) [INFO] [0m
[32m* 02-02:19:39 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 02-02:19:40 (3777) [INFO] Determining fastest mirrors[0m
[32m* 02-02:19:54 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 02-02:19:54 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 02-02:19:54 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 02-02:19:54 (3777) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 02-02:19:54 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 02-02:19:54 (3777) [INFO]  * extras: mirror.netdirekt.com.tr[0m
[32m* 02-02:19:54 (3777) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 02-02:20:24 (3787) [INFO] [0m
[32m* 02-02:20:24 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 02-02:20:24 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 02-02:20:24 (3767) [INFO] [0m
[32m* 02-02:20:24 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 02-02:20:26 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 02-02:20:26 (3787) [INFO] [0m
[32m* 02-02:20:26 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 02-02:20:26 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2RQODMI1dX/ea_profile.json[0m
[32m* 02-02:20:28 (1619) [INFO] Backed up EA4 profile to /tmp/2RQODMI1dX/ea_profile.json[0m
[33m* 02-02:20:28 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 02-02:20: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.

[0m
[33m* 02-02:20:33 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 04-02:26:17 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 04-02:26:17 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 04-02:26:17 (3767) [INFO] [0m
[32m* 04-02:26:17 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 04-02:26:17 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 04-02:26:17 (3777) [INFO]               : epel extras updates[0m
[32m* 04-02:26:17 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 04-02:26:17 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 04-02:26:17 (3787) [INFO] [0m
[32m* 04-02:26:17 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 04-02:26:17 (3767) [INFO] [0m
[32m* 04-02:26:18 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 04-02:26:18 (3777) [INFO] Determining fastest mirrors[0m
[32m* 04-02:26:24 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 04-02:26:24 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 04-02:26:24 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 04-02:26:24 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 04-02:26:24 (3777) [INFO]  * epel: mirror.alwyzon.net[0m
[32m* 04-02:26:24 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 04-02:26:24 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 04-02:26:45 (3787) [INFO] [0m
[32m* 04-02:26:45 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 04-02:26:45 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 04-02:26:45 (3767) [INFO] [0m
[32m* 04-02:26:45 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 04-02:26:46 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 04-02:26:46 (3787) [INFO] [0m
[32m* 04-02:26:46 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 04-02:26:46 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OV22ul0KU3/ea_profile.json[0m
[32m* 04-02:26:47 (1619) [INFO] Backed up EA4 profile to /tmp/OV22ul0KU3/ea_profile.json[0m
[33m* 04-02:26: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 04-02:26:48 (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.

[0m
[33m* 04-02:26:48 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 04-15:56:46 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 04-15:56:46 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 04-15:56:46 (3767) [INFO] [0m
[32m* 04-15:56:47 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 04-15:56:47 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 04-15:56:47 (3777) [INFO]               : epel extras updates[0m
[32m* 04-15:56:47 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 04-15:56:47 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 04-15:56:47 (3787) [INFO] [0m
[32m* 04-15:56:47 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 04-15:56:47 (3767) [INFO] [0m
[32m* 04-15:56:47 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 04-15:56:48 (3777) [INFO] Determining fastest mirrors[0m
[32m* 04-15:56:52 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 04-15:56:52 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 04-15:56:52 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 04-15:56:52 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 04-15:56:52 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 04-15:56:52 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 04-15:56:52 (3777) [INFO]  * updates: ftp.linux.org.tr[0m
[32m* 04-15:57:14 (3787) [INFO] [0m
[32m* 04-15:57:14 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 04-15:57:14 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 04-15:57:14 (3767) [INFO] [0m
[32m* 04-15:57:14 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 04-15:57:16 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 04-15:57:16 (3787) [INFO] [0m
[32m* 04-15:57:16 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 04-15:57:16 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qCuvcRr7H8/ea_profile.json[0m
[32m* 04-15:57:17 (1619) [INFO] Backed up EA4 profile to /tmp/qCuvcRr7H8/ea_profile.json[0m
[33m* 04-15:57: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 04-15:57: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.

[0m
[33m* 04-15:57:18 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 05-02:21:38 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 05-02:21:38 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 05-02:21:38 (3767) [INFO] [0m
[32m* 05-02:21:39 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 05-02:21:39 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 05-02:21:39 (3777) [INFO]               : epel extras updates[0m
[32m* 05-02:21:39 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 05-02:21:39 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 05-02:21:39 (3787) [INFO] [0m
[32m* 05-02:21:39 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 05-02:21:39 (3767) [INFO] [0m
[32m* 05-02:21:39 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 05-02:21:40 (3777) [INFO] Determining fastest mirrors[0m
[32m* 05-02:21:45 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 05-02:21:45 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 05-02:21:45 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 05-02:21:45 (3777) [INFO]  * base: mirror.onlinehosting.com.tr[0m
[32m* 05-02:21:45 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 05-02:21:45 (3777) [INFO]  * extras: mirror.netdirekt.com.tr[0m
[32m* 05-02:21:45 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 05-02:22:12 (3787) [INFO] [0m
[32m* 05-02:22:12 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 05-02:22:12 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 05-02:22:12 (3767) [INFO] [0m
[32m* 05-02:22:12 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 05-02:22:13 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 05-02:22:13 (3787) [INFO] [0m
[32m* 05-02:22:13 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 05-02:22:13 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_sI3qfQasb/ea_profile.json[0m
[32m* 05-02:22:14 (1619) [INFO] Backed up EA4 profile to /tmp/_sI3qfQasb/ea_profile.json[0m
[33m* 05-02:22:14 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 05-02:22:15 (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.

[0m
[33m* 05-02:22:15 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 06-02:25:55 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 06-02:25:55 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 06-02:25:55 (3767) [INFO] [0m
[32m* 06-02:25:55 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 06-02:25:56 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 06-02:25:56 (3777) [INFO]               : epel extras updates[0m
[32m* 06-02:25:56 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 06-02:25:56 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 06-02:25:56 (3787) [INFO] [0m
[32m* 06-02:25:56 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 06-02:25:56 (3767) [INFO] [0m
[32m* 06-02:25:56 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 06-02:25:57 (3777) [INFO] Determining fastest mirrors[0m
[32m* 06-02:26:06 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 06-02:26:06 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 06-02:26:06 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 06-02:26:06 (3777) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 06-02:26:06 (3777) [INFO]  * epel: epel.mirror.angkasa.id[0m
[32m* 06-02:26:06 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 06-02:26:06 (3777) [INFO]  * updates: ftp.linux.org.tr[0m
[32m* 06-02:26:16 (3777) [INFO] https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/18faed90515bd11d0c2a0afbd9c6881444b5ceb9c77a0122ca5a05dd43a361b5-updateinfo.xml.bz2: [Errno 14] HTTPS Error 500 - Internal Server Error[0m
[32m* 06-02:26:16 (3777) [INFO] Trying other mirror.[0m
[32m* 06-02:26:33 (3787) [INFO] [0m
[32m* 06-02:26:33 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 06-02:26:33 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 06-02:26:33 (3767) [INFO] [0m
[32m* 06-02:26:34 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 06-02:26:37 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 06-02:26:37 (3787) [INFO] [0m
[32m* 06-02:26:37 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 06-02:26:37 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PUNPN3TqFV/ea_profile.json[0m
[32m* 06-02:26:39 (1619) [INFO] Backed up EA4 profile to /tmp/PUNPN3TqFV/ea_profile.json[0m
[33m* 06-02:26: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 06-02:26: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.

[0m
[33m* 06-02:26:40 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 07-02:14:52 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 07-02:14:53 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 07-02:14:53 (3767) [INFO] [0m
[32m* 07-02:14:53 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 07-02:14:53 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 07-02:14:53 (3777) [INFO]               : epel extras updates[0m
[32m* 07-02:14:53 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 07-02:14:53 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 07-02:14:53 (3787) [INFO] [0m
[32m* 07-02:14:53 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 07-02:14:53 (3767) [INFO] [0m
[32m* 07-02:14:54 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 07-02:14:54 (3777) [INFO] Determining fastest mirrors[0m
[32m* 07-02:15:00 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 07-02:15:00 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 07-02:15:00 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 07-02:15:00 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 07-02:15:00 (3777) [INFO]  * epel: mirror.yer.az[0m
[32m* 07-02:15:00 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 07-02:15:00 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 07-02:15:27 (3787) [INFO] [0m
[32m* 07-02:15:27 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 07-02:15:27 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 07-02:15:27 (3767) [INFO] [0m
[32m* 07-02:15:27 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 07-02:15:29 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 07-02:15:29 (3787) [INFO] [0m
[32m* 07-02:15:29 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 07-02:15:29 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aSjiBj9ZC4/ea_profile.json[0m
[32m* 07-02:15:30 (1619) [INFO] Backed up EA4 profile to /tmp/aSjiBj9ZC4/ea_profile.json[0m
[33m* 07-02:15:30 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 07-02:15:31 (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.

[0m
[33m* 07-02:15:31 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 08-02:16:43 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 08-02:16:43 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 08-02:16:43 (3767) [INFO] [0m
[32m* 08-02:16:43 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 08-02:16:43 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 08-02:16:43 (3777) [INFO]               : epel extras updates[0m
[32m* 08-02:16:43 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 08-02:16:43 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 08-02:16:43 (3787) [INFO] [0m
[32m* 08-02:16:43 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 08-02:16:43 (3767) [INFO] [0m
[32m* 08-02:16:43 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 08-02:16:44 (3777) [INFO] Determining fastest mirrors[0m
[32m* 08-02:16:53 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 08-02:16:53 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 08-02:16:53 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 08-02:16:53 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 08-02:16:53 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 08-02:16:53 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 08-02:16:53 (3777) [INFO]  * updates: centos.vargonen.com[0m
[32m* 08-02:17:20 (3787) [INFO] [0m
[32m* 08-02:17:20 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 08-02:17:20 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 08-02:17:20 (3767) [INFO] [0m
[32m* 08-02:17:21 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 08-02:17:22 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 08-02:17:22 (3787) [INFO] [0m
[32m* 08-02:17:22 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 08-02:17:22 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SPAty4yHra/ea_profile.json[0m
[32m* 08-02:17:23 (1619) [INFO] Backed up EA4 profile to /tmp/SPAty4yHra/ea_profile.json[0m
[33m* 08-02:17:23 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 08-02:17:24 (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.

[0m
[33m* 08-02:17:24 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 09-02:17:21 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 09-02:17:21 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 09-02:17:21 (3767) [INFO] [0m
[32m* 09-02:17:21 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 09-02:17:21 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 09-02:17:21 (3777) [INFO]               : epel extras updates[0m
[32m* 09-02:17:21 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 09-02:17:21 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 09-02:17:21 (3787) [INFO] [0m
[32m* 09-02:17:21 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 09-02:17:21 (3767) [INFO] [0m
[32m* 09-02:17:21 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 09-02:17:22 (3777) [INFO] Determining fastest mirrors[0m
[32m* 09-02:17:31 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 09-02:17:31 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 09-02:17:31 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 09-02:17:31 (3777) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 09-02:17:31 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 09-02:17:31 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 09-02:17:31 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 09-02:17:56 (3787) [INFO] [0m
[32m* 09-02:17:56 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 09-02:17:56 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 09-02:17:56 (3767) [INFO] [0m
[32m* 09-02:17:56 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 09-02:17:57 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 09-02:17:57 (3787) [INFO] [0m
[32m* 09-02:17:57 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 09-02:17:57 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lD3F_dVcqL/ea_profile.json[0m
[32m* 09-02:17:58 (1619) [INFO] Backed up EA4 profile to /tmp/lD3F_dVcqL/ea_profile.json[0m
[33m* 09-02:17: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 09-02:17: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.

[0m
[33m* 09-02:17:59 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 10-02:13:43 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 10-02:13:44 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 10-02:13:44 (3767) [INFO] [0m
[32m* 10-02:13:44 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 10-02:13:44 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 10-02:13:44 (3777) [INFO]               : epel extras updates[0m
[32m* 10-02:13:44 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 10-02:13:44 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 10-02:13:44 (3787) [INFO] [0m
[32m* 10-02:13:44 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 10-02:13:44 (3767) [INFO] [0m
[32m* 10-02:13:45 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 10-02:13:45 (3777) [INFO] Determining fastest mirrors[0m
[32m* 10-02:13:50 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 10-02:13:50 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 10-02:13:50 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 10-02:13:50 (3777) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 10-02:13:50 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 10-02:13:50 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 10-02:13:50 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 10-02:14:15 (3787) [INFO] [0m
[32m* 10-02:14:15 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 10-02:14:15 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 10-02:14:15 (3767) [INFO] [0m
[32m* 10-02:14:16 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 10-02:14:17 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 10-02:14:17 (3787) [INFO] [0m
[32m* 10-02:14:17 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 10-02:14:17 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZtmcPptvD_/ea_profile.json[0m
[32m* 10-02:14:19 (1619) [INFO] Backed up EA4 profile to /tmp/ZtmcPptvD_/ea_profile.json[0m
[33m* 10-02:14:19 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 10-02:14:20 (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.

[0m
[33m* 10-02:14:20 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 11-02:16:32 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 11-02:16:33 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 11-02:16:33 (3767) [INFO] [0m
[32m* 11-02:16:33 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 11-02:16:33 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 11-02:16:33 (3777) [INFO]               : epel extras updates[0m
[32m* 11-02:16:33 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 11-02:16:33 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 11-02:16:33 (3787) [INFO] [0m
[32m* 11-02:16:33 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 11-02:16:33 (3767) [INFO] [0m
[32m* 11-02:16:33 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 11-02:16:34 (3777) [INFO] Determining fastest mirrors[0m
[32m* 11-02:16:39 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 11-02:16:39 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 11-02:16:39 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 11-02:16:39 (3777) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 11-02:16:39 (3777) [INFO]  * epel: mirror.telepoint.bg[0m
[32m* 11-02:16:39 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 11-02:16:39 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 11-02:17:04 (3777) [INFO] [0m
[32m* 11-02:17:04 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 11-02:17:04 (3787) [INFO] [0m
[33m* 11-02:17:04 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 11-02:17:04 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 11-02:17:04 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 11-02:17:04 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/k_VSgMiIZ5/ea_profile.json[0m
[32m* 11-02:17:05 (1619) [INFO] Backed up EA4 profile to /tmp/k_VSgMiIZ5/ea_profile.json[0m
[33m* 11-02:17: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 11-02:17: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.

[0m
[33m* 11-02:17:06 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 11-15:47:31 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 11-15:47:31 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 11-15:47:31 (3767) [INFO] [0m
[32m* 11-15:47:31 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 11-15:47:32 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 11-15:47:32 (3777) [INFO]               : epel extras updates[0m
[32m* 11-15:47:32 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 11-15:47:32 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 11-15:47:32 (3787) [INFO] [0m
[32m* 11-15:47:32 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 11-15:47:32 (3767) [INFO] [0m
[32m* 11-15:47:32 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 11-15:47:33 (3777) [INFO] Determining fastest mirrors[0m
[32m* 11-15:47:33 (3777) [INFO] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was[0m
[32m* 11-15:47:33 (3777) [INFO] 14: curl#6 - "Could not resolve host: httpupdate.cpanel.net; Name or service not known"[0m
[32m* 11-15:47:33 (3777) [INFO] [0m
[32m* 11-15:47:33 (3777) [INFO] [0m
[32m* 11-15:47:33 (3777) [INFO]  One of the configured repositories failed (Unknown),[0m
[32m* 11-15:47:33 (3777) [INFO]  and yum doesn't have enough cached data to continue. At this point the only[0m
[32m* 11-15:47:33 (3777) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:[0m
[32m* 11-15:47:33 (3777) [INFO] [0m
[32m* 11-15:47:33 (3777) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.[0m
[32m* 11-15:47:33 (3777) [INFO] [0m
[32m* 11-15:47:33 (3777) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working[0m
[32m* 11-15:47:33 (3777) [INFO]         upstream. This is most often useful if you are using a newer[0m
[32m* 11-15:47:33 (3777) [INFO]         distribution release than is supported by the repository (and the[0m
[32m* 11-15:47:33 (3777) [INFO]         packages for the previous distribution release still work).[0m
[32m* 11-15:47:33 (3777) [INFO] [0m
[32m* 11-15:47:33 (3777) [INFO]      3. Run the command with the repository temporarily disabled[0m
[32m* 11-15:47:33 (3777) [INFO]             yum --disablerepo=<repoid> ...[0m
[32m* 11-15:47:33 (3777) [INFO] [0m
[32m* 11-15:47:33 (3777) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum[0m
[32m* 11-15:47:33 (3777) [INFO]         will then just ignore the repository until you permanently enable it[0m
[32m* 11-15:47:33 (3777) [INFO]         again or use --enablerepo for temporary usage:[0m
[32m* 11-15:47:33 (3777) [INFO] [0m
[32m* 11-15:47:33 (3777) [INFO]             yum-config-manager --disable <repoid>[0m
[32m* 11-15:47:33 (3777) [INFO]         or[0m
[32m* 11-15:47:33 (3777) [INFO]             subscription-manager repos --disable=<repoid>[0m
[32m* 11-15:47:33 (3777) [INFO] [0m
[32m* 11-15:47:33 (3777) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.[0m
[32m* 11-15:47:33 (3777) [INFO]         Note that yum will try to contact the repo. when it runs most commands,[0m
[32m* 11-15:47:33 (3777) [INFO]         so will have to try and fail each time (and thus. yum will be be much[0m
[32m* 11-15:47:33 (3777) [INFO]         slower). If it is a very temporary problem though, this is often a nice[0m
[32m* 11-15:47:33 (3777) [INFO]         compromise:[0m
[32m* 11-15:47:33 (3777) [INFO] [0m
[32m* 11-15:47:33 (3777) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true[0m
[32m* 11-15:47:33 (3777) [INFO] [0m
[32m* 11-15:47:33 (3777) [INFO] Cannot find a valid baseurl for repo: EA4/7/x86_64[0m
[32m* 11-15:47:33 (3787) [INFO] [0m
[33m* 11-15:47:33 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 11-15:47:33 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 11-15:47:33 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 11-15:47:33 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jb5Ig06CXb/ea_profile.json[0m
[32m* 11-15:47:55 (1619) [INFO] Backed up EA4 profile to /tmp/jb5Ig06CXb/ea_profile.json[0m
[33m* 11-15:47: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 11-15:47:56 (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.

[0m
[33m* 11-15:47:56 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 12-02:17:48 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 12-02:17:48 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 12-02:17:48 (3767) [INFO] [0m
[32m* 12-02:17:49 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 12-02:17:49 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 12-02:17:49 (3777) [INFO]               : epel extras updates[0m
[32m* 12-02:17:49 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 12-02:17:49 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 12-02:17:49 (3787) [INFO] [0m
[32m* 12-02:17:49 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 12-02:17:49 (3767) [INFO] [0m
[32m* 12-02:17:50 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 12-02:17:50 (3777) [INFO] Determining fastest mirrors[0m
[32m* 12-02:17:55 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 12-02:17:55 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 12-02:17:55 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 12-02:17:55 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 12-02:17:55 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 12-02:17:55 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 12-02:17:55 (3777) [INFO]  * updates: mirror.netdirekt.com.tr[0m
[32m* 12-02:18:21 (3777) [INFO] [0m
[32m* 12-02:18:21 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 12-02:18:22 (3787) [INFO] [0m
[33m* 12-02:18:22 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 12-02:18:22 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 12-02:18:22 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 12-02:18:22 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WQUqChug0D/ea_profile.json[0m
[32m* 12-02:18:26 (1619) [INFO] Backed up EA4 profile to /tmp/WQUqChug0D/ea_profile.json[0m
[33m* 12-02:18: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 12-02:18:27 (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.

[0m
[33m* 12-02:18:27 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 13-02:15:06 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 13-02:15:06 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 13-02:15:06 (3767) [INFO] [0m
[32m* 13-02:15:07 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 13-02:15:07 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 13-02:15:07 (3777) [INFO]               : epel extras updates[0m
[32m* 13-02:15:10 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 13-02:15:10 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 13-02:15:10 (3787) [INFO] [0m
[32m* 13-02:15:10 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 13-02:15:10 (3767) [INFO] [0m
[32m* 13-02:15:10 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 13-02:15:11 (3777) [INFO] Determining fastest mirrors[0m
[32m* 13-02:15:15 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 13-02:15:15 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 13-02:15:15 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 13-02:15:15 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 13-02:15:15 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 13-02:15:15 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 13-02:15:15 (3777) [INFO]  * updates: ftp.linux.org.tr[0m
[32m* 13-02:15:38 (3777) [INFO] [0m
[32m* 13-02:15:38 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 13-02:15:38 (3787) [INFO] [0m
[33m* 13-02:15:38 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 13-02:15:38 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 13-02:15:38 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 13-02:15:38 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FiQerZi_fm/ea_profile.json[0m
[32m* 13-02:15:40 (1619) [INFO] Backed up EA4 profile to /tmp/FiQerZi_fm/ea_profile.json[0m
[33m* 13-02:15: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 13-02:15:41 (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.

[0m
[33m* 13-02:15:41 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 14-02:14:43 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 14-02:14:43 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 14-02:14:43 (3767) [INFO] [0m
[32m* 14-02:14:43 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 14-02:14:43 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 14-02:14:43 (3777) [INFO]               : epel extras updates[0m
[32m* 14-02:14:44 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 14-02:14:44 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 14-02:14:44 (3787) [INFO] [0m
[32m* 14-02:14:44 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 14-02:14:44 (3767) [INFO] [0m
[32m* 14-02:14:44 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 14-02:14:45 (3777) [INFO] Determining fastest mirrors[0m
[32m* 14-02:14:49 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 14-02:14:49 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 14-02:14:49 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 14-02:14:49 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 14-02:14:49 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 14-02:14:49 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 14-02:14:49 (3777) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 14-02:15:13 (3777) [INFO] [0m
[32m* 14-02:15:13 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 14-02:15:13 (3787) [INFO] [0m
[33m* 14-02:15:13 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 14-02:15:13 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 14-02:15:14 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 14-02:15:14 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/n2fxUFlc96/ea_profile.json[0m
[32m* 14-02:15:16 (1619) [INFO] Backed up EA4 profile to /tmp/n2fxUFlc96/ea_profile.json[0m
[33m* 14-02:15: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 14-02:15: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.

[0m
[33m* 14-02:15:18 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 15-02:17:28 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 15-02:17:29 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 15-02:17:29 (3767) [INFO] [0m
[32m* 15-02:17:30 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 15-02:17:30 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 15-02:17:30 (3777) [INFO]               : epel extras updates[0m
[32m* 15-02:17:30 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 15-02:17:30 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 15-02:17:30 (3787) [INFO] [0m
[32m* 15-02:17:30 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 15-02:17:30 (3767) [INFO] [0m
[32m* 15-02:17:31 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 15-02:17:31 (3777) [INFO] Determining fastest mirrors[0m
[32m* 15-02:17:35 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 15-02:17:35 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 15-02:17:35 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 15-02:17:35 (3777) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 15-02:17:35 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 15-02:17:35 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 15-02:17:35 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 15-02:18:08 (3777) [INFO] [0m
[32m* 15-02:18:08 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 15-02:18:09 (3787) [INFO] [0m
[33m* 15-02:18:09 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 15-02:18:09 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 15-02:18:09 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 15-02:18:09 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/X9VmkvBXh6/ea_profile.json[0m
[32m* 15-02:18:10 (1619) [INFO] Backed up EA4 profile to /tmp/X9VmkvBXh6/ea_profile.json[0m
[33m* 15-02:18: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 15-02:18:11 (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.

[0m
[33m* 15-02:18:11 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 16-02:14:02 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 16-02:14:02 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 16-02:14:02 (3767) [INFO] [0m
[32m* 16-02:14:02 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 16-02:14:02 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 16-02:14:02 (3777) [INFO]               : epel extras updates[0m
[32m* 16-02:14:02 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 16-02:14:02 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 16-02:14:02 (3787) [INFO] [0m
[32m* 16-02:14:02 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 16-02:14:02 (3767) [INFO] [0m
[32m* 16-02:14:02 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 16-02:14:03 (3777) [INFO] Determining fastest mirrors[0m
[32m* 16-02:14:08 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 16-02:14:08 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 16-02:14:08 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 16-02:14:08 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 16-02:14:08 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 16-02:14:08 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 16-02:14:08 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 16-02:14:42 (3777) [INFO] [0m
[32m* 16-02:14:42 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 16-02:14:42 (3787) [INFO] [0m
[33m* 16-02:14:42 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 16-02:14:42 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 16-02:14:42 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 16-02:14:42 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8Mhv1E84OC/ea_profile.json[0m
[32m* 16-02:14:44 (1619) [INFO] Backed up EA4 profile to /tmp/8Mhv1E84OC/ea_profile.json[0m
[33m* 16-02:14:44 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 16-02:14:45 (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.

[0m
[33m* 16-02:14:45 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 17-02:12:45 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 17-02:12:45 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 17-02:12:45 (3767) [INFO] [0m
[32m* 17-02:12:45 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 17-02:12:45 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 17-02:12:45 (3777) [INFO]               : epel extras updates[0m
[32m* 17-02:12:46 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 17-02:12:46 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 17-02:12:46 (3787) [INFO] [0m
[32m* 17-02:12:46 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 17-02:12:46 (3767) [INFO] [0m
[32m* 17-02:12:46 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 17-02:12:46 (3777) [INFO] Determining fastest mirrors[0m
[32m* 17-02:12:51 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 17-02:12:51 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 17-02:12:51 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 17-02:12:51 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 17-02:12:51 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 17-02:12:51 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 17-02:12:51 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 17-02:13:21 (3777) [INFO] [0m
[32m* 17-02:13:21 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 17-02:13:22 (3787) [INFO] [0m
[33m* 17-02:13:22 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 17-02:13:22 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 17-02:13:22 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 17-02:13:22 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/r_K9fXZUQg/ea_profile.json[0m
[32m* 17-02:13:23 (1619) [INFO] Backed up EA4 profile to /tmp/r_K9fXZUQg/ea_profile.json[0m
[33m* 17-02:13:23 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 17-02:13:24 (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.

[0m
[33m* 17-02:13:24 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 18-02:14:53 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 18-02:14:53 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 18-02:14:53 (3767) [INFO] [0m
[32m* 18-02:14:53 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 18-02:14:53 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 18-02:14:53 (3777) [INFO]               : epel extras updates[0m
[32m* 18-02:14:53 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 18-02:14:53 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 18-02:14:53 (3787) [INFO] [0m
[32m* 18-02:14:53 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 18-02:14:53 (3767) [INFO] [0m
[32m* 18-02:14:54 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 18-02:14:54 (3777) [INFO] Determining fastest mirrors[0m
[32m* 18-02:14:59 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 18-02:14:59 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 18-02:14:59 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 18-02:14:59 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 18-02:14:59 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 18-02:14:59 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 18-02:14:59 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 18-02:15:19 (3777) [INFO] [0m
[32m* 18-02:15:19 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 18-02:15:19 (3787) [INFO] [0m
[33m* 18-02:15:19 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 18-02:15:19 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 18-02:15:19 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 18-02:15:19 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vlrpZrsgxw/ea_profile.json[0m
[32m* 18-02:15:21 (1619) [INFO] Backed up EA4 profile to /tmp/vlrpZrsgxw/ea_profile.json[0m
[33m* 18-02:15:21 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 18-02:15:22 (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.

[0m
[33m* 18-02:15:22 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 18-15:48:44 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 18-15:48:44 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 18-15:48:44 (3767) [INFO] [0m
[32m* 18-15:48:44 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 18-15:48:44 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 18-15:48:44 (3777) [INFO]               : epel extras updates[0m
[32m* 18-15:48:44 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 18-15:48:44 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 18-15:48:44 (3787) [INFO] [0m
[32m* 18-15:48:44 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 18-15:48:44 (3767) [INFO] [0m
[32m* 18-15:48:45 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 18-15:48:45 (3777) [INFO] Determining fastest mirrors[0m
[32m* 18-15:48:51 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 18-15:48:51 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 18-15:48:51 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 18-15:48:51 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 18-15:48:51 (3777) [INFO]  * epel: ftp.fi.muni.cz[0m
[32m* 18-15:48:51 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 18-15:48:51 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 18-15:49:17 (3777) [INFO] [0m
[32m* 18-15:49:17 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 18-15:49:17 (3787) [INFO] [0m
[33m* 18-15:49:17 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 18-15:49:17 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 18-15:49:17 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 18-15:49:17 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/02TWcgN1tV/ea_profile.json[0m
[32m* 18-15:49:18 (1619) [INFO] Backed up EA4 profile to /tmp/02TWcgN1tV/ea_profile.json[0m
[33m* 18-15:49: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 18-15:49:19 (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.

[0m
[33m* 18-15:49:19 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 19-02:48:34 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 19-02:48:34 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 19-02:48:34 (3767) [INFO] [0m
[32m* 19-02:48:35 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 19-02:48:35 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 19-02:48:35 (3777) [INFO]               : epel extras updates[0m
[32m* 19-02:48:35 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 19-02:48:35 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 19-02:48:35 (3787) [INFO] [0m
[32m* 19-02:48:35 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 19-02:48:35 (3767) [INFO] [0m
[32m* 19-02:48:35 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 19-02:48:36 (3777) [INFO] Determining fastest mirrors[0m
[32m* 19-02:48:45 (3777) [INFO]  * EA4: 93.115.203.100[0m
[32m* 19-02:48:45 (3777) [INFO]  * cpanel-addons-production-feed: 93.115.203.100[0m
[32m* 19-02:48:45 (3777) [INFO]  * cpanel-plugins: 93.115.203.100[0m
[32m* 19-02:48:45 (3777) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 19-02:48:45 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 19-02:48:45 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 19-02:48:45 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 19-02:49:12 (3777) [INFO] [0m
[32m* 19-02:49:12 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 19-02:49:12 (3787) [INFO] [0m
[33m* 19-02:49:12 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 19-02:49:12 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 19-02:49:12 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 19-02:49:12 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/t_6mRsFADe/ea_profile.json[0m
[32m* 19-02:49:13 (1619) [INFO] Backed up EA4 profile to /tmp/t_6mRsFADe/ea_profile.json[0m
[33m* 19-02:49:13 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 19-02:49:15 (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.

[0m
[33m* 19-02:49:15 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 20-02:16:40 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 20-02:16:40 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 20-02:16:40 (3767) [INFO] [0m
[32m* 20-02:16:40 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 20-02:16:40 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 20-02:16:40 (3777) [INFO]               : epel extras updates[0m
[32m* 20-02:16:41 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 20-02:16:41 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 20-02:16:41 (3787) [INFO] [0m
[32m* 20-02:16:41 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 20-02:16:41 (3767) [INFO] [0m
[32m* 20-02:16:41 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 20-02:16:42 (3777) [INFO] Determining fastest mirrors[0m
[32m* 20-02:16:46 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 20-02:16:46 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 20-02:16:46 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 20-02:16:46 (3777) [INFO]  * base: mirror.onlinehosting.com.tr[0m
[32m* 20-02:16:46 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 20-02:16:46 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 20-02:16:46 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 20-02:17:09 (3777) [INFO] [0m
[32m* 20-02:17:09 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 20-02:17:09 (3787) [INFO] [0m
[33m* 20-02:17:09 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 20-02:17:09 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 20-02:17:09 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 20-02:17:09 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6GgSpchpY3/ea_profile.json[0m
[32m* 20-02:17:13 (1619) [INFO] Backed up EA4 profile to /tmp/6GgSpchpY3/ea_profile.json[0m
[33m* 20-02:17:13 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 20-02:17:14 (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.

[0m
[33m* 20-02:17:14 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 21-02:13:45 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 21-02:13:45 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 21-02:13:45 (3767) [INFO] [0m
[32m* 21-02:13:45 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 21-02:13:45 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 21-02:13:45 (3777) [INFO]               : epel extras updates[0m
[32m* 21-02:13:45 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 21-02:13:45 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 21-02:13:45 (3787) [INFO] [0m
[32m* 21-02:13:45 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 21-02:13:45 (3767) [INFO] [0m
[32m* 21-02:13:45 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 21-02:13:46 (3777) [INFO] Determining fastest mirrors[0m
[32m* 21-02:13:53 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 21-02:13:53 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 21-02:13:53 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 21-02:13:53 (3777) [INFO]  * base: mirror.onlinehosting.com.tr[0m
[32m* 21-02:13:53 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 21-02:13:53 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 21-02:13:53 (3777) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 21-02:14:21 (3777) [INFO] [0m
[32m* 21-02:14:21 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 21-02:14:21 (3787) [INFO] [0m
[33m* 21-02:14:21 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 21-02:14:21 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 21-02:14:21 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 21-02:14:21 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9dFkI5BzG8/ea_profile.json[0m
[32m* 21-02:14:23 (1619) [INFO] Backed up EA4 profile to /tmp/9dFkI5BzG8/ea_profile.json[0m
[33m* 21-02:14:23 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 21-02:14:24 (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.

[0m
[33m* 21-02:14:24 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 22-02:15:02 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 22-02:15:02 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 22-02:15:02 (3767) [INFO] [0m
[32m* 22-02:15:02 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 22-02:15:02 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 22-02:15:02 (3777) [INFO]               : epel extras updates[0m
[32m* 22-02:15:02 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 22-02:15:02 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 22-02:15:02 (3787) [INFO] [0m
[32m* 22-02:15:02 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 22-02:15:02 (3767) [INFO] [0m
[32m* 22-02:15:03 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 22-02:15:03 (3777) [INFO] Determining fastest mirrors[0m
[32m* 22-02:15:07 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 22-02:15:07 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 22-02:15:07 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 22-02:15:07 (3777) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 22-02:15:07 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 22-02:15:07 (3777) [INFO]  * extras: mirror.netdirekt.com.tr[0m
[32m* 22-02:15:07 (3777) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 22-02:15:28 (3777) [INFO] [0m
[32m* 22-02:15:28 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 22-02:15:28 (3787) [INFO] [0m
[33m* 22-02:15:28 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 22-02:15:28 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 22-02:15:28 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 22-02:15:28 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3_oq0CyxFx/ea_profile.json[0m
[32m* 22-02:15:30 (1619) [INFO] Backed up EA4 profile to /tmp/3_oq0CyxFx/ea_profile.json[0m
[33m* 22-02:15:30 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 22-02:15:31 (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.

[0m
[33m* 22-02:15:31 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 23-02:12:55 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 23-02:12:55 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 23-02:12:55 (3767) [INFO] [0m
[32m* 23-02:12:55 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 23-02:12:55 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 23-02:12:55 (3777) [INFO]               : epel extras updates[0m
[32m* 23-02:12:56 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 23-02:12:56 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 23-02:12:56 (3787) [INFO] [0m
[32m* 23-02:12:56 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 23-02:12:56 (3767) [INFO] [0m
[32m* 23-02:12:56 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 23-02:12:56 (3777) [INFO] Determining fastest mirrors[0m
[32m* 23-02:13:01 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 23-02:13:01 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 23-02:13:01 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 23-02:13:01 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 23-02:13:01 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 23-02:13:01 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 23-02:13:01 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 23-02:13:24 (3777) [INFO] [0m
[32m* 23-02:13:24 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 23-02:13:24 (3787) [INFO] [0m
[33m* 23-02:13:24 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 23-02:13:24 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 23-02:13:24 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 23-02:13:24 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/74xCcotXbq/ea_profile.json[0m
[32m* 23-02:13:25 (1619) [INFO] Backed up EA4 profile to /tmp/74xCcotXbq/ea_profile.json[0m
[33m* 23-02:13:25 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 23-02:13:26 (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.

[0m
[33m* 23-02:13:26 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 24-02:18:27 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 24-02:18:27 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 24-02:18:27 (3767) [INFO] [0m
[32m* 24-02:18:28 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 24-02:18:28 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 24-02:18:28 (3777) [INFO]               : epel extras updates[0m
[32m* 24-02:18:28 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 24-02:18:28 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 24-02:18:28 (3787) [INFO] [0m
[32m* 24-02:18:28 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 24-02:18:28 (3767) [INFO] [0m
[32m* 24-02:18:28 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 24-02:18:29 (3777) [INFO] Determining fastest mirrors[0m
[32m* 24-02:18:34 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 24-02:18:34 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 24-02:18:34 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 24-02:18:34 (3777) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 24-02:18:34 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 24-02:18:34 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 24-02:18:34 (3777) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 24-02:19:03 (3777) [INFO] [0m
[32m* 24-02:19:03 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 24-02:19:03 (3787) [INFO] [0m
[33m* 24-02:19:03 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 24-02:19:03 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 24-02:19:03 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 24-02:19:03 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VqesSfw9Bj/ea_profile.json[0m
[32m* 24-02:19:05 (1619) [INFO] Backed up EA4 profile to /tmp/VqesSfw9Bj/ea_profile.json[0m
[33m* 24-02:19: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 24-02:19: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.

[0m
[33m* 24-02:19:06 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 25-02:12:48 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 25-02:12:48 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 25-02:12:48 (3767) [INFO] [0m
[32m* 25-02:12:48 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 25-02:12:48 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 25-02:12:48 (3777) [INFO]               : epel extras updates[0m
[32m* 25-02:12:49 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 25-02:12:49 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 25-02:12:49 (3787) [INFO] [0m
[32m* 25-02:12:49 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 25-02:12:49 (3767) [INFO] [0m
[32m* 25-02:12:49 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 25-02:12:50 (3777) [INFO] Determining fastest mirrors[0m
[32m* 25-02:12:55 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 25-02:12:55 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 25-02:12:55 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 25-02:12:55 (3777) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 25-02:12:55 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 25-02:12:55 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 25-02:12:55 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 25-02:13:17 (3777) [INFO] [0m
[32m* 25-02:13:17 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 25-02:13:17 (3787) [INFO] [0m
[33m* 25-02:13:17 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 25-02:13:17 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 25-02:13:17 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 25-02:13:17 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/anapxenxA_/ea_profile.json[0m
[32m* 25-02:13:18 (1619) [INFO] Backed up EA4 profile to /tmp/anapxenxA_/ea_profile.json[0m
[33m* 25-02:13: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 25-02:13:19 (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.

[0m
[33m* 25-02:13:19 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 25-15:49:47 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 25-15:49:47 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 25-15:49:47 (3767) [INFO] [0m
[32m* 25-15:49:47 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 25-15:49:47 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 25-15:49:47 (3777) [INFO]               : epel extras updates[0m
[32m* 25-15:49:47 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 25-15:49:47 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 25-15:49:47 (3787) [INFO] [0m
[32m* 25-15:49:47 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 25-15:49:47 (3767) [INFO] [0m
[32m* 25-15:49:47 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 25-15:49:48 (3777) [INFO] Determining fastest mirrors[0m
[32m* 25-15:49:53 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 25-15:49:53 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 25-15:49:53 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 25-15:49:53 (3777) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 25-15:49:53 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 25-15:49:53 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 25-15:49:53 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 25-15:50:14 (3777) [INFO] [0m
[32m* 25-15:50:14 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 25-15:50:14 (3787) [INFO] [0m
[33m* 25-15:50:14 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 25-15:50:14 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 25-15:50:14 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 25-15:50:14 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/kSY6Vuyq8d/ea_profile.json[0m
[32m* 25-15:50:15 (1619) [INFO] Backed up EA4 profile to /tmp/kSY6Vuyq8d/ea_profile.json[0m
[33m* 25-15:50:15 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 25-15:50:16 (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.

[0m
[33m* 25-15:50:16 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 26-02:13:58 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 26-02:13:58 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 26-02:13:58 (3767) [INFO] [0m
[32m* 26-02:13:58 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 26-02:13:58 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 26-02:13:58 (3777) [INFO]               : epel extras updates[0m
[32m* 26-02:13:58 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 26-02:13:59 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 26-02:13:59 (3787) [INFO] [0m
[32m* 26-02:13:59 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 26-02:13:59 (3767) [INFO] [0m
[32m* 26-02:13:59 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 26-02:13:59 (3777) [INFO] Determining fastest mirrors[0m
[32m* 26-02:14:05 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 26-02:14:05 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 26-02:14:05 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 26-02:14:05 (3777) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 26-02:14:05 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 26-02:14:05 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 26-02:14:05 (3777) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 26-02:14:36 (3777) [INFO] [0m
[32m* 26-02:14:36 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 26-02:14:36 (3787) [INFO] [0m
[33m* 26-02:14:36 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 26-02:14:36 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 26-02:14:36 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 26-02:14:36 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/CrYq0o_8B0/ea_profile.json[0m
[32m* 26-02:14:37 (1619) [INFO] Backed up EA4 profile to /tmp/CrYq0o_8B0/ea_profile.json[0m
[33m* 26-02:14:37 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 26-02:14:38 (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.

[0m
[33m* 26-02:14:38 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 27-02:13:24 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 27-02:13:24 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 27-02:13:24 (3767) [INFO] [0m
[32m* 27-02:13:25 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 27-02:13:25 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 27-02:13:25 (3777) [INFO]               : epel extras updates[0m
[32m* 27-02:13:25 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 27-02:13:25 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 27-02:13:25 (3787) [INFO] [0m
[32m* 27-02:13:25 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 27-02:13:25 (3767) [INFO] [0m
[32m* 27-02:13:25 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 27-02:13:26 (3777) [INFO] Determining fastest mirrors[0m
[32m* 27-02:13:31 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 27-02:13:31 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 27-02:13:31 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 27-02:13:31 (3777) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 27-02:13:31 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 27-02:13:31 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 27-02:13:31 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 27-02:13:54 (3777) [INFO] [0m
[32m* 27-02:13:54 (3777) [INFO] kernel.x86_64                    3.10.0-1160.80.1.el7                    updates[0m
[32m* 27-02:13:54 (3787) [INFO] [0m
[33m* 27-02:13:54 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 27-02:13:54 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 27-02:13:54 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 27-02:13:54 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WbxCNozR7p/ea_profile.json[0m
[32m* 27-02:13:56 (1619) [INFO] Backed up EA4 profile to /tmp/WbxCNozR7p/ea_profile.json[0m
[33m* 27-02:13: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 27-02:13:57 (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.

[0m
[33m* 27-02:13:57 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 27-10:29:20 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 27-10:29:20 (3473) [ERROR] http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/84bcedc43cf12869a6d4fb0500a04292fc62d090d771315bbbc49c80a27edbe8-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/.

[0m
[33m* 27-10:29:20 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 27-10:29:21 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 27-10:29:21 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 27-10:29:21 (3767) [INFO] [0m
[32m* 27-10:29:21 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 27-10:29:21 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 27-10:29:21 (3777) [INFO]               : epel extras updates[0m
[32m* 27-10:29:21 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 27-10:29:21 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 27-10:29:21 (3787) [INFO] [0m
[32m* 27-10:29:21 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 27-10:29:21 (3767) [INFO] [0m
[32m* 27-10:29:22 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 27-10:29:22 (3777) [INFO] Determining fastest mirrors[0m
[32m* 27-10:29:42 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 27-10:29:42 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 27-10:29:42 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 27-10:29:42 (3777) [INFO]  * base: ftp.linux.org.tr[0m
[32m* 27-10:29:42 (3777) [INFO]  * epel: epel.mirror.angkasa.id[0m
[32m* 27-10:29:42 (3777) [INFO]  * extras: mirror.rabisu.com[0m
[32m* 27-10:29:42 (3777) [INFO]  * updates: ftp.linux.org.tr[0m
[32m* 27-10:29:52 (3777) [INFO] https://mirrors.thzhost.com/epel/7/x86_64/repodata/7468745d4c24de043b337382b23a99dac5394b21e29bd927ceb0045f3799c4bf-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found[0m
[32m* 27-10:29:52 (3777) [INFO] Trying other mirror.[0m
[32m* 27-10:29:52 (3777) [INFO] To address this issue please refer to the below wiki article [0m
[32m* 27-10:29:52 (3777) [INFO] [0m
[32m* 27-10:29:52 (3777) [INFO] https://wiki.centos.org/yum-errors[0m
[32m* 27-10:29:52 (3777) [INFO] [0m
[32m* 27-10:29:52 (3777) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.[0m
[32m* 27-10:29:52 (3777) [INFO] [0m
[32m* 27-10:29:52 (3777) [INFO] https://repo.extreme-ix.org/epel/7/x86_64/repodata/222882460a2d67499e33832c65d0d11f9256817cff35b88662e0bb900a5166d1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found[0m
[32m* 27-10:29:52 (3777) [INFO] Trying other mirror.[0m
[32m* 27-10:29:54 (3777) [INFO] https://mirrors.thzhost.com/epel/7/x86_64/repodata/222882460a2d67499e33832c65d0d11f9256817cff35b88662e0bb900a5166d1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found[0m
[32m* 27-10:29:54 (3777) [INFO] Trying other mirror.[0m
[32m* 27-10:29:59 (3777) [INFO] http://epel.mirror.angkasa.id/pub/epel/7/x86_64/repodata/7468745d4c24de043b337382b23a99dac5394b21e29bd927ceb0045f3799c4bf-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found[0m
[32m* 27-10:29:59 (3777) [INFO] Trying other mirror.[0m
[32m* 27-10:30:13 (3787) [INFO] [0m
[32m* 27-10:30:13 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 27-10:30:13 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 27-10:30:13 (3767) [INFO] [0m
[32m* 27-10:30:14 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 27-10:30:15 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 27-10:30:15 (3787) [INFO] [0m
[32m* 27-10:30:15 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 27-10:30:15 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FOej5Q7UnR/ea_profile.json[0m
[32m* 27-10:30:17 (1619) [INFO] Backed up EA4 profile to /tmp/FOej5Q7UnR/ea_profile.json[0m
[33m* 27-10:30: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 27-10:30: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.

[0m
[33m* 27-10:30:18 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 28-02:13:54 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 28-02:13:54 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 28-02:13:54 (3767) [INFO] [0m
[32m* 28-02:13:54 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 28-02:13:54 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 28-02:13:54 (3777) [INFO]               : epel extras updates[0m
[32m* 28-02:13:54 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 28-02:13:54 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 28-02:13:54 (3787) [INFO] [0m
[32m* 28-02:13:54 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 28-02:13:54 (3767) [INFO] [0m
[32m* 28-02:13:54 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 28-02:13:55 (3777) [INFO] Determining fastest mirrors[0m
[32m* 28-02:14:00 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 28-02:14:00 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 28-02:14:00 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 28-02:14:00 (3777) [INFO]  * base: mirror.onlinehosting.com.tr[0m
[32m* 28-02:14:00 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 28-02:14:00 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 28-02:14:00 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 28-02:14:25 (3787) [INFO] [0m
[32m* 28-02:14:25 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 28-02:14:25 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 28-02:14:25 (3767) [INFO] [0m
[32m* 28-02:14:25 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 28-02:14:26 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 28-02:14:26 (3787) [INFO] [0m
[32m* 28-02:14:26 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 28-02:14:26 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/X5mO2HThkq/ea_profile.json[0m
[32m* 28-02:14:29 (1619) [INFO] Backed up EA4 profile to /tmp/X5mO2HThkq/ea_profile.json[0m
[33m* 28-02:14:29 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 28-02:14:30 (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.

[0m
[33m* 28-02:14:30 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 29-02:14:38 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 29-02:14:38 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 29-02:14:38 (3767) [INFO] [0m
[32m* 29-02:14:39 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 29-02:14:39 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 29-02:14:39 (3777) [INFO]               : epel extras updates[0m
[32m* 29-02:14:39 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 29-02:14:39 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 29-02:14:39 (3787) [INFO] [0m
[32m* 29-02:14:39 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 29-02:14:39 (3767) [INFO] [0m
[32m* 29-02:14:39 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 29-02:14:40 (3777) [INFO] Determining fastest mirrors[0m
[32m* 29-02:14:45 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 29-02:14:45 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 29-02:14:45 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 29-02:14:45 (3777) [INFO]  * base: mirror.radoreservers.com[0m
[32m* 29-02:14:45 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 29-02:14:45 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 29-02:14:45 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 29-02:15:15 (3787) [INFO] [0m
[32m* 29-02:15:15 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 29-02:15:15 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 29-02:15:15 (3767) [INFO] [0m
[32m* 29-02:15:15 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 29-02:15:17 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 29-02:15:17 (3787) [INFO] [0m
[32m* 29-02:15:17 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 29-02:15:17 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8G5tt8CMjF/ea_profile.json[0m
[32m* 29-02:15:19 (1619) [INFO] Backed up EA4 profile to /tmp/8G5tt8CMjF/ea_profile.json[0m
[33m* 29-02:15:19 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 29-02:15:19 (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.

[0m
[33m* 29-02:15:20 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 30-02:13:00 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 30-02:13:00 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 30-02:13:00 (3767) [INFO] [0m
[32m* 30-02:13:00 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 30-02:13:00 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 30-02:13:00 (3777) [INFO]               : epel extras updates[0m
[32m* 30-02:13:00 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 30-02:13:00 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 30-02:13:00 (3787) [INFO] [0m
[32m* 30-02:13:00 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 30-02:13:00 (3767) [INFO] [0m
[32m* 30-02:13:01 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 30-02:13:01 (3777) [INFO] Determining fastest mirrors[0m
[32m* 30-02:13:06 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 30-02:13:06 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 30-02:13:06 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 30-02:13:06 (3777) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 30-02:13:06 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 30-02:13:06 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 30-02:13:06 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 30-02:13:28 (3787) [INFO] [0m
[32m* 30-02:13:28 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 30-02:13:28 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 30-02:13:28 (3767) [INFO] [0m
[32m* 30-02:13:28 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 30-02:13:29 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 30-02:13:29 (3787) [INFO] [0m
[32m* 30-02:13:29 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 30-02:13:29 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qVUGMLTp12/ea_profile.json[0m
[32m* 30-02:13:31 (1619) [INFO] Backed up EA4 profile to /tmp/qVUGMLTp12/ea_profile.json[0m
[33m* 30-02:13:31 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 30-02:13:31 (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.

[0m
[33m* 30-02:13:32 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 01-02:12:49 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 01-02:12:49 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 01-02:12:49 (3767) [INFO] [0m
[32m* 01-02:12:49 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 01-02:12:49 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 01-02:12:49 (3777) [INFO]               : epel extras updates[0m
[32m* 01-02:12:49 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 01-02:12:49 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 01-02:12:49 (3787) [INFO] [0m
[32m* 01-02:12:49 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 01-02:12:49 (3767) [INFO] [0m
[32m* 01-02:12:49 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 01-02:12:50 (3777) [INFO] Determining fastest mirrors[0m
[32m* 01-02:12:55 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 01-02:12:55 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 01-02:12:55 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 01-02:12:55 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 01-02:12:55 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 01-02:12:55 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 01-02:12:55 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 01-02:13:21 (3787) [INFO] [0m
[32m* 01-02:13:21 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 01-02:13:21 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 01-02:13:21 (3767) [INFO] [0m
[32m* 01-02:13:21 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 01-02:13:22 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 01-02:13:22 (3787) [INFO] [0m
[32m* 01-02:13:22 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 01-02:13:22 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cJ8OgpqbSq/ea_profile.json[0m
[32m* 01-02:13:23 (1619) [INFO] Backed up EA4 profile to /tmp/cJ8OgpqbSq/ea_profile.json[0m
[33m* 01-02:13:23 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 01-02:13:24 (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.

[0m
[33m* 01-02:13:24 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 02-02:17:56 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 02-02:17:56 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 02-02:17:56 (3767) [INFO] [0m
[32m* 02-02:17:57 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 02-02:17:57 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 02-02:17:57 (3777) [INFO]               : epel extras updates[0m
[32m* 02-02:17:57 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 02-02:17:57 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 02-02:17:57 (3787) [INFO] [0m
[32m* 02-02:17:57 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 02-02:17:57 (3767) [INFO] [0m
[32m* 02-02:17:57 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 02-02:17:58 (3777) [INFO] Determining fastest mirrors[0m
[32m* 02-02:18:05 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 02-02:18:05 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 02-02:18:05 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 02-02:18:05 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 02-02:18:05 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 02-02:18:05 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 02-02:18:05 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 02-02:18:49 (3787) [INFO] [0m
[32m* 02-02:18:49 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 02-02:18:49 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 02-02:18:49 (3767) [INFO] [0m
[32m* 02-02:18:49 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 02-02:18:50 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 02-02:18:50 (3787) [INFO] [0m
[32m* 02-02:18:50 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 02-02:18:50 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qadJliKaUZ/ea_profile.json[0m
[32m* 02-02:18:51 (1619) [INFO] Backed up EA4 profile to /tmp/qadJliKaUZ/ea_profile.json[0m
[33m* 02-02:18:51 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 02-02:18:52 (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.

[0m
[33m* 02-02:18:52 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 02-15:48:08 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 02-15:48:08 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 02-15:48:08 (3767) [INFO] [0m
[32m* 02-15:48:08 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 02-15:48:08 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 02-15:48:08 (3777) [INFO]               : epel extras updates[0m
[32m* 02-15:48:09 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 02-15:48:09 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 02-15:48:09 (3787) [INFO] [0m
[32m* 02-15:48:09 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 02-15:48:09 (3767) [INFO] [0m
[32m* 02-15:48:09 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 02-15:48:09 (3777) [INFO] Determining fastest mirrors[0m
[32m* 02-15:48:14 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 02-15:48:14 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 02-15:48:14 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 02-15:48:14 (3777) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 02-15:48:14 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 02-15:48:14 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 02-15:48:14 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 02-15:48:36 (3787) [INFO] [0m
[32m* 02-15:48:36 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 02-15:48:36 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 02-15:48:36 (3767) [INFO] [0m
[32m* 02-15:48:36 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 02-15:48:38 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 02-15:48:38 (3787) [INFO] [0m
[32m* 02-15:48:38 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 02-15:48:38 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Q47ThD__R4/ea_profile.json[0m
[32m* 02-15:48:39 (1619) [INFO] Backed up EA4 profile to /tmp/Q47ThD__R4/ea_profile.json[0m
[33m* 02-15:48: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 02-15:48:40 (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.

[0m
[33m* 02-15:48:40 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 03-02:13:56 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 03-02:13:56 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 03-02:13:56 (3767) [INFO] [0m
[32m* 03-02:13:57 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 03-02:13:57 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 03-02:13:57 (3777) [INFO]               : epel extras updates[0m
[32m* 03-02:13:57 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 03-02:13:57 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 03-02:13:57 (3787) [INFO] [0m
[32m* 03-02:13:57 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 03-02:13:57 (3767) [INFO] [0m
[32m* 03-02:13:57 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 03-02:13:58 (3777) [INFO] Determining fastest mirrors[0m
[32m* 03-02:14:04 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 03-02:14:04 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 03-02:14:04 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 03-02:14:04 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 03-02:14:04 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 03-02:14:04 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 03-02:14:04 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 03-02:14:25 (3787) [INFO] [0m
[32m* 03-02:14:25 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 03-02:14:25 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 03-02:14:25 (3767) [INFO] [0m
[32m* 03-02:14:25 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 03-02:14:26 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 03-02:14:26 (3787) [INFO] [0m
[32m* 03-02:14:26 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 03-02:14:26 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2ILMI3KTuf/ea_profile.json[0m
[32m* 03-02:14:28 (1619) [INFO] Backed up EA4 profile to /tmp/2ILMI3KTuf/ea_profile.json[0m
[33m* 03-02:14:28 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 03-02:14:29 (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.

[0m
[33m* 03-02:14:29 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 04-02:17:49 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 04-02:17:49 (3473) [ERROR] http://mirror.netdirekt.com.tr/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: mirror.netdirekt.com.tr; No address associated with hostname"
Trying other mirror.
[0m
[33m* 04-02:17:49 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 04-02:17:49 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 04-02:17:49 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 04-02:17:49 (3767) [INFO] [0m
[32m* 04-02:17:50 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 04-02:17:50 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 04-02:17:50 (3777) [INFO]               : epel extras updates[0m
[32m* 04-02:17:50 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 04-02:17:50 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 04-02:17:50 (3787) [INFO] [0m
[32m* 04-02:17:50 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 04-02:17:50 (3767) [INFO] [0m
[32m* 04-02:17:50 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 04-02:17:51 (3777) [INFO] Determining fastest mirrors[0m
[32m* 04-02:18:11 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 04-02:18:11 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 04-02:18:11 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 04-02:18:11 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 04-02:18:11 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 04-02:18:11 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 04-02:18:11 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 04-02:18:51 (3787) [INFO] [0m
[32m* 04-02:18:51 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 04-02:18:51 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 04-02:18:51 (3767) [INFO] [0m
[32m* 04-02:18:51 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 04-02:18:53 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 04-02:18:53 (3787) [INFO] [0m
[32m* 04-02:18:53 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 04-02:18:53 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/J54_bE_dQI/ea_profile.json[0m
[32m* 04-02:18:54 (1619) [INFO] Backed up EA4 profile to /tmp/J54_bE_dQI/ea_profile.json[0m
[33m* 04-02:18:54 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 04-02:18:55 (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.

[0m
[33m* 04-02:18:55 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 05-02:18:29 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 05-02:18:29 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 05-02:18:29 (3767) [INFO] [0m
[32m* 05-02:18:29 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 05-02:18:29 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 05-02:18:29 (3777) [INFO]               : epel extras updates[0m
[32m* 05-02:18:30 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 05-02:18:30 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 05-02:18:30 (3787) [INFO] [0m
[32m* 05-02:18:30 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 05-02:18:30 (3767) [INFO] [0m
[32m* 05-02:18:30 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 05-02:18:30 (3777) [INFO] Determining fastest mirrors[0m
[32m* 05-02:18:35 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 05-02:18:35 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 05-02:18:35 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 05-02:18:35 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 05-02:18:35 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 05-02:18:35 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 05-02:18:35 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 05-02:19:02 (3787) [INFO] [0m
[32m* 05-02:19:02 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 05-02:19:02 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 05-02:19:02 (3767) [INFO] [0m
[32m* 05-02:19:02 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 05-02:19:03 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 05-02:19:03 (3787) [INFO] [0m
[32m* 05-02:19:03 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 05-02:19:03 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JVyJb71801/ea_profile.json[0m
[32m* 05-02:19:04 (1619) [INFO] Backed up EA4 profile to /tmp/JVyJb71801/ea_profile.json[0m
[33m* 05-02:19:04 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 05-02:19:05 (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.

[0m
[33m* 05-02:19:05 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 06-02:17:52 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 06-02:17:53 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 06-02:17:53 (3767) [INFO] [0m
[32m* 06-02:17:54 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 06-02:17:54 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 06-02:17:54 (3777) [INFO]               : epel extras updates[0m
[32m* 06-02:17:54 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 06-02:17:54 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 06-02:17:54 (3787) [INFO] [0m
[32m* 06-02:17:54 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 06-02:17:54 (3767) [INFO] [0m
[32m* 06-02:17:55 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 06-02:17:56 (3777) [INFO] Determining fastest mirrors[0m
[32m* 06-02:18:17 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 06-02:18:17 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 06-02:18:17 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 06-02:18:17 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 06-02:18:17 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 06-02:18:17 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 06-02:18:17 (3777) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 06-02:18:57 (3787) [INFO] [0m
[32m* 06-02:18:57 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 06-02:18:57 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 06-02:18:57 (3767) [INFO] [0m
[32m* 06-02:18:57 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 06-02:18:58 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 06-02:18:58 (3787) [INFO] [0m
[32m* 06-02:18:58 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 06-02:18:59 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0EZ0y7kp9F/ea_profile.json[0m
[32m* 06-02:19:00 (1619) [INFO] Backed up EA4 profile to /tmp/0EZ0y7kp9F/ea_profile.json[0m
[33m* 06-02:19:00 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 06-02:19: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.

[0m
[33m* 06-02:19:01 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 07-02:15:22 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 07-02:15:22 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 07-02:15:22 (3767) [INFO] [0m
[32m* 07-02:15:22 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 07-02:15:22 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 07-02:15:22 (3777) [INFO]               : epel extras updates[0m
[32m* 07-02:15:22 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 07-02:15:22 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 07-02:15:22 (3787) [INFO] [0m
[32m* 07-02:15:22 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 07-02:15:22 (3767) [INFO] [0m
[32m* 07-02:15:23 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 07-02:15:23 (3777) [INFO] Determining fastest mirrors[0m
[32m* 07-02:15:28 (3777) [INFO]  * EA4: 185.157.208.252[0m
[32m* 07-02:15:28 (3777) [INFO]  * cpanel-addons-production-feed: 185.157.208.252[0m
[32m* 07-02:15:28 (3777) [INFO]  * cpanel-plugins: 185.157.208.252[0m
[32m* 07-02:15:28 (3777) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 07-02:15:28 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 07-02:15:28 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 07-02:15:28 (3777) [INFO]  * updates: mirror.netdirekt.com.tr[0m
[32m* 07-02:15:50 (3787) [INFO] [0m
[32m* 07-02:15:50 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 07-02:15:50 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 07-02:15:50 (3767) [INFO] [0m
[32m* 07-02:15:51 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 07-02:15:52 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 07-02:15:52 (3787) [INFO] [0m
[32m* 07-02:15:52 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 07-02:15:52 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EvCTDYaCTc/ea_profile.json[0m
[32m* 07-02:15:53 (1619) [INFO] Backed up EA4 profile to /tmp/EvCTDYaCTc/ea_profile.json[0m
[33m* 07-02:15:53 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 07-02:15:54 (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.

[0m
[33m* 07-02:15:54 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 08-02:14:17 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 08-02:14:17 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 08-02:14:17 (3767) [INFO] [0m
[32m* 08-02:14:17 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 08-02:14:17 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 08-02:14:17 (3777) [INFO]               : epel extras updates[0m
[32m* 08-02:14:17 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 08-02:14:17 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 08-02:14:17 (3787) [INFO] [0m
[32m* 08-02:14:17 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 08-02:14:17 (3767) [INFO] [0m
[32m* 08-02:14:18 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 08-02:14:18 (3777) [INFO] Determining fastest mirrors[0m
[32m* 08-02:14:22 (3777) [INFO]  * EA4: 185.157.208.252[0m
[32m* 08-02:14:22 (3777) [INFO]  * cpanel-addons-production-feed: 185.157.208.252[0m
[32m* 08-02:14:22 (3777) [INFO]  * cpanel-plugins: 185.157.208.252[0m
[32m* 08-02:14:22 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 08-02:14:22 (3777) [INFO]  * epel: epel.mirror.angkasa.id[0m
[32m* 08-02:14:22 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 08-02:14:22 (3777) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 08-02:14:44 (3787) [INFO] [0m
[32m* 08-02:14:44 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 08-02:14:44 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 08-02:14:44 (3767) [INFO] [0m
[32m* 08-02:14:45 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 08-02:14:46 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 08-02:14:46 (3787) [INFO] [0m
[32m* 08-02:14:46 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 08-02:14:46 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Vp9S48BQDp/ea_profile.json[0m
[32m* 08-02:14:47 (1619) [INFO] Backed up EA4 profile to /tmp/Vp9S48BQDp/ea_profile.json[0m
[33m* 08-02:14: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 08-02:14:48 (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.

[0m
[33m* 08-02:14:48 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 09-02:28:29 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 09-02:28:29 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 09-02:28:29 (3767) [INFO] [0m
[32m* 09-02:28:30 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 09-02:28:30 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 09-02:28:30 (3777) [INFO]               : epel extras updates[0m
[32m* 09-02:28:30 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 09-02:28:30 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 09-02:28:30 (3787) [INFO] [0m
[32m* 09-02:28:30 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 09-02:28:30 (3767) [INFO] [0m
[32m* 09-02:28:30 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 09-02:28:31 (3777) [INFO] Determining fastest mirrors[0m
[32m* 09-02:28:46 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 09-02:28:46 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 09-02:28:46 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 09-02:28:46 (3777) [INFO]  * base: mirror.netdirekt.com.tr[0m
[32m* 09-02:28:46 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 09-02:28:46 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 09-02:28:46 (3777) [INFO]  * updates: mirror.netdirekt.com.tr[0m
[32m* 09-02:29:02 (3777) [INFO] http://centos.vargonen.com/centos/7.9.2009/updates/x86_64/repodata/786e8dfe79441eaea10aac32f5cccb17a51796051e6eebb88345d7dc4b24e3bd-primary.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"[0m
[32m* 09-02:29:02 (3777) [INFO] Trying other mirror.[0m
[32m* 09-02:32:47 (3787) [INFO] [0m
[32m* 09-02:32:47 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 09-02:32:47 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 09-02:32:47 (3767) [INFO] [0m
[32m* 09-02:32:47 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 09-02:32:49 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 09-02:32:49 (3787) [INFO] [0m
[32m* 09-02:32:49 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 09-02:32:49 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XuAbWuARQi/ea_profile.json[0m
[32m* 09-02:32:50 (1619) [INFO] Backed up EA4 profile to /tmp/XuAbWuARQi/ea_profile.json[0m
[33m* 09-02:32: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 09-02:32:51 (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.

[0m
[33m* 09-02:32:51 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 09-15:48:02 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 09-15:48:02 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 09-15:48:02 (3767) [INFO] [0m
[32m* 09-15:48:02 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 09-15:48:02 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 09-15:48:02 (3777) [INFO]               : epel extras updates[0m
[32m* 09-15:48:02 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 09-15:48:02 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 09-15:48:02 (3787) [INFO] [0m
[32m* 09-15:48:02 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 09-15:48:02 (3767) [INFO] [0m
[32m* 09-15:48:03 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 09-15:48:03 (3777) [INFO] Determining fastest mirrors[0m
[32m* 09-15:48:19 (3777) [INFO]  * EA4: 185.157.208.252[0m
[32m* 09-15:48:19 (3777) [INFO]  * cpanel-addons-production-feed: 185.157.208.252[0m
[32m* 09-15:48:19 (3777) [INFO]  * cpanel-plugins: 185.157.208.252[0m
[32m* 09-15:48:19 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 09-15:48:19 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 09-15:48:19 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 09-15:48:19 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 09-15:48:42 (3787) [INFO] [0m
[32m* 09-15:48:42 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 09-15:48:42 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 09-15:48:42 (3767) [INFO] [0m
[32m* 09-15:48:42 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 09-15:48:43 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 09-15:48:44 (3787) [INFO] [0m
[32m* 09-15:48:44 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 09-15:48:44 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ev3kFnUvuJ/ea_profile.json[0m
[32m* 09-15:48:45 (1619) [INFO] Backed up EA4 profile to /tmp/Ev3kFnUvuJ/ea_profile.json[0m
[33m* 09-15:48: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 09-15:48: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.

[0m
[33m* 09-15:48:46 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 10-02:14:40 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 10-02:14:40 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 10-02:14:40 (3767) [INFO] [0m
[32m* 10-02:14:40 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 10-02:14:41 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 10-02:14:41 (3777) [INFO]               : epel extras updates[0m
[32m* 10-02:14:41 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 10-02:14:41 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 10-02:14:41 (3787) [INFO] [0m
[32m* 10-02:14:41 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 10-02:14:41 (3767) [INFO] [0m
[32m* 10-02:14:41 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 10-02:14:42 (3777) [INFO] Determining fastest mirrors[0m
[32m* 10-02:14:52 (3777) [INFO]  * EA4: 185.157.208.252[0m
[32m* 10-02:14:52 (3777) [INFO]  * cpanel-addons-production-feed: 185.157.208.252[0m
[32m* 10-02:14:52 (3777) [INFO]  * cpanel-plugins: 185.157.208.252[0m
[32m* 10-02:14:52 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 10-02:14:52 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 10-02:14:52 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 10-02:14:52 (3777) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 10-02:15:15 (3787) [INFO] [0m
[32m* 10-02:15:15 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 10-02:15:15 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 10-02:15:15 (3767) [INFO] [0m
[32m* 10-02:15:16 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 10-02:15:17 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 10-02:15:17 (3787) [INFO] [0m
[32m* 10-02:15:17 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 10-02:15:17 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BL6g1RuhGy/ea_profile.json[0m
[32m* 10-02:15:19 (1619) [INFO] Backed up EA4 profile to /tmp/BL6g1RuhGy/ea_profile.json[0m
[33m* 10-02:15:19 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 10-02:15:20 (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.

[0m
[33m* 10-02:15:20 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 11-02:20:35 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 11-02:20:35 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 11-02:20:35 (3767) [INFO] [0m
[32m* 11-02:20:35 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 11-02:20:35 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 11-02:20:35 (3777) [INFO]               : epel extras updates[0m
[32m* 11-02:20:36 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 11-02:20:36 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 11-02:20:36 (3787) [INFO] [0m
[32m* 11-02:20:36 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 11-02:20:36 (3767) [INFO] [0m
[32m* 11-02:20:36 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 11-02:20:37 (3777) [INFO] Determining fastest mirrors[0m
[32m* 11-02:21:09 (3777) [INFO]  * EA4: 185.157.208.252[0m
[32m* 11-02:21:09 (3777) [INFO]  * cpanel-addons-production-feed: 185.157.208.252[0m
[32m* 11-02:21:09 (3777) [INFO]  * cpanel-plugins: 185.157.208.252[0m
[32m* 11-02:21:09 (3777) [INFO]  * base: mirror.onlinehosting.com.tr[0m
[32m* 11-02:21:09 (3777) [INFO]  * epel: ftp.yz.yamagata-u.ac.jp[0m
[32m* 11-02:21:09 (3777) [INFO]  * extras: mirror.verinomi.com[0m
[32m* 11-02:21:09 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 11-02:22:07 (3787) [INFO] [0m
[32m* 11-02:22:07 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 11-02:22:07 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 11-02:22:07 (3767) [INFO] [0m
[32m* 11-02:22:07 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 11-02:22:09 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 11-02:22:09 (3787) [INFO] [0m
[32m* 11-02:22:09 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 11-02:22:09 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2yEIug7Sni/ea_profile.json[0m
[32m* 11-02:22:10 (1619) [INFO] Backed up EA4 profile to /tmp/2yEIug7Sni/ea_profile.json[0m
[33m* 11-02:22: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 11-02:22:16 (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.

[0m
[33m* 11-02:22:16 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 12-02:14:06 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 12-02:14:06 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 12-02:14:06 (3767) [INFO] [0m
[32m* 12-02:14:06 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 12-02:14:06 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 12-02:14:06 (3777) [INFO]               : epel extras updates[0m
[32m* 12-02:14:07 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 12-02:14:07 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 12-02:14:07 (3787) [INFO] [0m
[32m* 12-02:14:07 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 12-02:14:07 (3767) [INFO] [0m
[32m* 12-02:14:07 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 12-02:14:08 (3777) [INFO] Determining fastest mirrors[0m
[32m* 12-02:14:11 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 12-02:14:11 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 12-02:14:11 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 12-02:14:11 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 12-02:14:11 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 12-02:14:11 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 12-02:14:11 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 12-02:14:36 (3787) [INFO] [0m
[32m* 12-02:14:36 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 12-02:14:36 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 12-02:14:36 (3767) [INFO] [0m
[32m* 12-02:14:37 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 12-02:14:44 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 12-02:14:44 (3787) [INFO] [0m
[32m* 12-02:14:44 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 12-02:14:44 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wT136_Y0fc/ea_profile.json[0m
[32m* 12-02:14:46 (1619) [INFO] Backed up EA4 profile to /tmp/wT136_Y0fc/ea_profile.json[0m
[33m* 12-02:14:46 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 12-02:14: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.

[0m
[33m* 12-02:14:47 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 13-02:18:52 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 13-02:18:52 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 13-02:18:52 (3767) [INFO] [0m
[32m* 13-02:18:53 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 13-02:18:53 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 13-02:18:53 (3777) [INFO]               : epel extras updates[0m
[32m* 13-02:18:53 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 13-02:18:53 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 13-02:18:53 (3787) [INFO] [0m
[32m* 13-02:18:53 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 13-02:18:53 (3767) [INFO] [0m
[32m* 13-02:18:53 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 13-02:18:54 (3777) [INFO] Determining fastest mirrors[0m
[32m* 13-02:18:59 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 13-02:18:59 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 13-02:18:59 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 13-02:18:59 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 13-02:18:59 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 13-02:18:59 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 13-02:18:59 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 13-02:20:38 (3777) [INFO] http://centos.turhost.com/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://centos.turhost.com/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')[0m
[32m* 13-02:20:38 (3777) [INFO] Trying other mirror.[0m
[32m* 13-02:20:54 (3787) [INFO] [0m
[32m* 13-02:20:54 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 13-02:20:54 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 13-02:20:54 (3767) [INFO] [0m
[32m* 13-02:20:54 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 13-02:20:55 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 13-02:20:55 (3787) [INFO] [0m
[32m* 13-02:20:55 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 13-02:20:55 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/32hdo8qB4D/ea_profile.json[0m
[32m* 13-02:20:57 (1619) [INFO] Backed up EA4 profile to /tmp/32hdo8qB4D/ea_profile.json[0m
[33m* 13-02:20: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 13-02:20:58 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 13-02:20:58 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 14-02:15:01 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 14-02:15:01 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 14-02:15:01 (3767) [INFO] [0m
[32m* 14-02:15:01 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 14-02:15:01 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 14-02:15:01 (3777) [INFO]               : epel extras updates[0m
[32m* 14-02:15:01 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 14-02:15:01 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 14-02:15:01 (3787) [INFO] [0m
[32m* 14-02:15:01 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 14-02:15:01 (3767) [INFO] [0m
[32m* 14-02:15:02 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 14-02:15:02 (3777) [INFO] Determining fastest mirrors[0m
[32m* 14-02:15:08 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 14-02:15:08 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 14-02:15:08 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 14-02:15:08 (3777) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 14-02:15:08 (3777) [INFO]  * epel: mirror.yer.az[0m
[32m* 14-02:15:08 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 14-02:15:08 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 14-02:15:39 (3787) [INFO] [0m
[32m* 14-02:15:39 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 14-02:15:39 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 14-02:15:39 (3767) [INFO] [0m
[32m* 14-02:15:39 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 14-02:15:40 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 14-02:15:40 (3787) [INFO] [0m
[32m* 14-02:15:40 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 14-02:15:40 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/egVvnvgSyu/ea_profile.json[0m
[32m* 14-02:15:42 (1619) [INFO] Backed up EA4 profile to /tmp/egVvnvgSyu/ea_profile.json[0m
[33m* 14-02:15: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 14-02:15:43 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 14-02:15:43 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 15-02:16:14 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 15-02:16:14 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 15-02:16:14 (3767) [INFO] [0m
[32m* 15-02:16:14 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 15-02:16:14 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 15-02:16:14 (3777) [INFO]               : epel extras updates[0m
[32m* 15-02:16:14 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 15-02:16:14 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 15-02:16:14 (3787) [INFO] [0m
[32m* 15-02:16:14 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 15-02:16:14 (3767) [INFO] [0m
[32m* 15-02:16:15 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 15-02:16:15 (3777) [INFO] Determining fastest mirrors[0m
[32m* 15-02:16:19 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 15-02:16:19 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 15-02:16:19 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 15-02:16:19 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 15-02:16:19 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 15-02:16:19 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 15-02:16:19 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 15-02:16:50 (3787) [INFO] [0m
[32m* 15-02:16:50 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 15-02:16:50 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 15-02:16:50 (3767) [INFO] [0m
[32m* 15-02:16:50 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 15-02:16:52 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 15-02:16:52 (3787) [INFO] [0m
[32m* 15-02:16:52 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 15-02:16:52 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xem7wZiI0N/ea_profile.json[0m
[32m* 15-02:16:53 (1619) [INFO] Backed up EA4 profile to /tmp/xem7wZiI0N/ea_profile.json[0m
[33m* 15-02:16:53 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 15-02:16:54 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 15-02:16:54 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 16-02:14:38 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 16-02:14:38 (3473) [ERROR] http://epel.mirror.angkasa.id/pub/epel/7/x86_64/repodata/c9bd6d85a979ae40b92a37defc449f680e473acff4b533a2cfb662199e348fdd-prestodelta.xml.gz: [Errno 12] Timeout on http://epel.mirror.angkasa.id/pub/epel/7/x86_64/repodata/c9bd6d85a979ae40b92a37defc449f680e473acff4b533a2cfb662199e348fdd-prestodelta.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
[0m
[33m* 16-02:14:38 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 16-02:14:39 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 16-02:14:39 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 16-02:14:39 (3767) [INFO] [0m
[32m* 16-02:14:39 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 16-02:14:39 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 16-02:14:39 (3777) [INFO]               : epel extras updates[0m
[32m* 16-02:14:40 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 16-02:14:40 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 16-02:14:40 (3787) [INFO] [0m
[32m* 16-02:14:40 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 16-02:14:40 (3767) [INFO] [0m
[32m* 16-02:14:40 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 16-02:14:40 (3777) [INFO] Determining fastest mirrors[0m
[32m* 16-02:14:46 (3777) [INFO]  * EA4: 185.157.208.252[0m
[32m* 16-02:14:46 (3777) [INFO]  * cpanel-addons-production-feed: 185.157.208.252[0m
[32m* 16-02:14:46 (3777) [INFO]  * cpanel-plugins: 185.157.208.252[0m
[32m* 16-02:14:46 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 16-02:14:46 (3777) [INFO]  * epel: mirror.yer.az[0m
[32m* 16-02:14:46 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 16-02:14:46 (3777) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 16-02:15:31 (3787) [INFO] [0m
[32m* 16-02:15:31 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 16-02:15:31 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 16-02:15:31 (3767) [INFO] [0m
[32m* 16-02:15:31 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 16-02:15:33 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 16-02:15:33 (3787) [INFO] [0m
[32m* 16-02:15:33 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 16-02:15:33 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/F_0fUSg0Y4/ea_profile.json[0m
[32m* 16-02:15:34 (1619) [INFO] Backed up EA4 profile to /tmp/F_0fUSg0Y4/ea_profile.json[0m
[33m* 16-02:15:34 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 16-02:15:35 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 16-02:15:35 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 16-15:59:12 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 16-15:59:12 (3473) [ERROR] http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/82dccd4839e7ab82fa9b0e7d11e545ead299296a12a3ddfcfdde153509db4bde-other.sqlite.bz2: [Errno 12] Timeout on http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/82dccd4839e7ab82fa9b0e7d11e545ead299296a12a3ddfcfdde153509db4bde-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
[0m
[33m* 16-15:59:12 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 16-15:59:12 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 16-15:59:12 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 16-15:59:12 (3767) [INFO] [0m
[32m* 16-15:59:13 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 16-15:59:13 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 16-15:59:13 (3777) [INFO]               : epel extras updates[0m
[32m* 16-15:59:13 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 16-15:59:13 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 16-15:59:13 (3787) [INFO] [0m
[32m* 16-15:59:13 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 16-15:59:13 (3767) [INFO] [0m
[32m* 16-15:59:13 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 16-15:59:14 (3777) [INFO] Determining fastest mirrors[0m
[32m* 16-15:59:19 (3777) [INFO]  * EA4: 185.157.208.252[0m
[32m* 16-15:59:19 (3777) [INFO]  * cpanel-addons-production-feed: 185.157.208.252[0m
[32m* 16-15:59:19 (3777) [INFO]  * cpanel-plugins: 185.157.208.252[0m
[32m* 16-15:59:19 (3777) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 16-15:59:19 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 16-15:59:19 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 16-15:59:19 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 16-16:00:06 (3777) [INFO] https://linux.domainesia.com/fedora/fedora-epel/7/x86_64/repodata/3dd50b7963def8e8bdaeb2f64f9ac466884d9b7fc598c7c0ce597a69ea7ee6e8-primary.sqlite.bz2: [Errno 12] Timeout on https://linux.domainesia.com/fedora/fedora-epel/7/x86_64/repodata/3dd50b7963def8e8bdaeb2f64f9ac466884d9b7fc598c7c0ce597a69ea7ee6e8-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')[0m
[32m* 16-16:00:06 (3777) [INFO] Trying other mirror.[0m
[32m* 16-16:00:34 (3777) [INFO] http://mirror.netdirekt.com.tr/centos/7.9.2009/updates/x86_64/repodata/2058c65bf2a799278bdf4adbf09c2a6638a8627896295881820b30eb6200adff-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.netdirekt.com.tr/centos/7.9.2009/updates/x86_64/repodata/2058c65bf2a799278bdf4adbf09c2a6638a8627896295881820b30eb6200adff-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')[0m
[32m* 16-16:00:34 (3777) [INFO] Trying other mirror.[0m
[32m* 16-16:00:35 (3777) [INFO] https://mirror.nevacloud.com/fedora/fedora-epel/7/x86_64/repodata/f4d2f67c6993f27ded722f64ddd6bfad49d83e38bebdf7cdbf19fc9903ebb154-updateinfo.xml.bz2: [Errno 12] Timeout on https://mirror.nevacloud.com/fedora/fedora-epel/7/x86_64/repodata/f4d2f67c6993f27ded722f64ddd6bfad49d83e38bebdf7cdbf19fc9903ebb154-updateinfo.xml.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')[0m
[32m* 16-16:00:35 (3777) [INFO] Trying other mirror.[0m
[32m* 16-16:01:32 (3777) [INFO] http://mirror.verinomi.com/centos/7.9.2009/updates/x86_64/repodata/2058c65bf2a799278bdf4adbf09c2a6638a8627896295881820b30eb6200adff-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.verinomi.com/centos/7.9.2009/updates/x86_64/repodata/2058c65bf2a799278bdf4adbf09c2a6638a8627896295881820b30eb6200adff-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')[0m
[32m* 16-16:01:32 (3777) [INFO] Trying other mirror.[0m
[32m* 16-16:02:23 (3787) [INFO] [0m
[32m* 16-16:02:23 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 16-16:02:23 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 16-16:02:23 (3767) [INFO] [0m
[32m* 16-16:02:23 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 16-16:02:25 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 16-16:02:25 (3787) [INFO] [0m
[32m* 16-16:02:27 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 16-16:02:27 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/p8M_obYVug/ea_profile.json[0m
[32m* 16-16:02:28 (1619) [INFO] Backed up EA4 profile to /tmp/p8M_obYVug/ea_profile.json[0m
[33m* 16-16:02:28 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 16-16:02:29 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 16-16:02:29 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 17-02:17:34 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 17-02:17:34 (3473) [ERROR] https://mirror.sabay.com.kh/epel/7/x86_64/repodata/cfaca0d612fffbde1862d82c05a286a71a6a3ed346e76036c622b99a25bf92a1-filelists.sqlite.bz2: [Errno 12] Timeout on https://mirror.sabay.com.kh/epel/7/x86_64/repodata/cfaca0d612fffbde1862d82c05a286a71a6a3ed346e76036c622b99a25bf92a1-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
[0m
[33m* 17-02:17:34 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 17-02:17:35 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 17-02:17:35 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 17-02:17:35 (3767) [INFO] [0m
[32m* 17-02:17:38 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 17-02:17:38 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 17-02:17:38 (3777) [INFO]               : epel extras updates[0m
[32m* 17-02:17:40 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 17-02:17:40 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 17-02:17:40 (3787) [INFO] [0m
[32m* 17-02:17:40 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 17-02:17:40 (3767) [INFO] [0m
[32m* 17-02:17:40 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 17-02:17:41 (3777) [INFO] Determining fastest mirrors[0m
[32m* 17-02:17:45 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 17-02:17:45 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 17-02:17:45 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 17-02:17:45 (3777) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 17-02:17:45 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 17-02:17:45 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 17-02:17:45 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 17-02:18:25 (3787) [INFO] [0m
[32m* 17-02:18:25 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 17-02:18:25 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 17-02:18:25 (3767) [INFO] [0m
[32m* 17-02:18:26 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 17-02:18:27 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 17-02:18:27 (3787) [INFO] [0m
[32m* 17-02:18:27 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 17-02:18:27 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/kFf4UfmsHV/ea_profile.json[0m
[32m* 17-02:18:29 (1619) [INFO] Backed up EA4 profile to /tmp/kFf4UfmsHV/ea_profile.json[0m
[33m* 17-02:18:29 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 17-02:18:30 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 17-02:18:33 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 18-02:21:47 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 18-02:21:47 (3473) [ERROR] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/65d7f3e6f8116d60ab4a288bbc9b5d6d3d3e0aa02588d54ba7d76d8c8ac05916-other.sqlite.bz2: [Errno 12] Timeout on http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/65d7f3e6f8116d60ab4a288bbc9b5d6d3d3e0aa02588d54ba7d76d8c8ac05916-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
[0m
[33m* 18-02:21:47 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 18-02:21:48 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 18-02:21:48 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 18-02:21:48 (3767) [INFO] [0m
[32m* 18-02:21:48 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 18-02:21:48 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 18-02:21:48 (3777) [INFO]               : epel extras updates[0m
[32m* 18-02:21:49 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 18-02:21:49 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 18-02:21:49 (3787) [INFO] [0m
[32m* 18-02:21:49 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 18-02:21:49 (3767) [INFO] [0m
[32m* 18-02:21:49 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 18-02:21:50 (3777) [INFO] Determining fastest mirrors[0m
[32m* 18-02:21:54 (3777) [INFO]  * EA4: 185.157.208.252[0m
[32m* 18-02:21:54 (3777) [INFO]  * cpanel-addons-production-feed: 185.157.208.252[0m
[32m* 18-02:21:54 (3777) [INFO]  * cpanel-plugins: 185.157.208.252[0m
[32m* 18-02:21:54 (3777) [INFO]  * base: mirror.sh.com.tr[0m
[32m* 18-02:21:54 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 18-02:21:54 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 18-02:21:54 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 18-02:22:19 (3777) [INFO] http://centos.vargonen.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"[0m
[32m* 18-02:22:19 (3777) [INFO] Trying other mirror.[0m
[32m* 18-02:22:50 (3777) [INFO] http://mirror.rabisu.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.rabisu.com/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')[0m
[32m* 18-02:22:50 (3777) [INFO] Trying other mirror.[0m
[32m* 18-02:23:07 (3787) [INFO] [0m
[32m* 18-02:23:07 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 18-02:23:07 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 18-02:23:07 (3767) [INFO] [0m
[32m* 18-02:23:07 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 18-02:23:08 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 18-02:23:08 (3787) [INFO] [0m
[32m* 18-02:23:08 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 18-02:23:08 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aSkWbh40Wz/ea_profile.json[0m
[32m* 18-02:23:10 (1619) [INFO] Backed up EA4 profile to /tmp/aSkWbh40Wz/ea_profile.json[0m
[33m* 18-02:23: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 18-02:23:11 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 18-02:23:11 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 19-02:15:03 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 19-02:15:03 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 19-02:15:03 (3767) [INFO] [0m
[32m* 19-02:15:04 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 19-02:15:04 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 19-02:15:04 (3777) [INFO]               : epel extras updates[0m
[32m* 19-02:15:04 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 19-02:15:04 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 19-02:15:04 (3787) [INFO] [0m
[32m* 19-02:15:04 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 19-02:15:04 (3767) [INFO] [0m
[32m* 19-02:15:04 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 19-02:15:05 (3777) [INFO] Determining fastest mirrors[0m
[32m* 19-02:15:10 (3777) [INFO]  * EA4: 185.157.208.252[0m
[32m* 19-02:15:10 (3777) [INFO]  * cpanel-addons-production-feed: 185.157.208.252[0m
[32m* 19-02:15:10 (3777) [INFO]  * cpanel-plugins: 185.157.208.252[0m
[32m* 19-02:15:10 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 19-02:15:10 (3777) [INFO]  * epel: mirror.yer.az[0m
[32m* 19-02:15:10 (3777) [INFO]  * extras: mirror.netdirekt.com.tr[0m
[32m* 19-02:15:10 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 19-02:15:35 (3787) [INFO] [0m
[32m* 19-02:15:35 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 19-02:15:35 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 19-02:15:35 (3767) [INFO] [0m
[32m* 19-02:15:35 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 19-02:15:36 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 19-02:15:36 (3787) [INFO] [0m
[32m* 19-02:15:36 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 19-02:15:36 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cCgWaIrYFD/ea_profile.json[0m
[32m* 19-02:15:38 (1619) [INFO] Backed up EA4 profile to /tmp/cCgWaIrYFD/ea_profile.json[0m
[33m* 19-02:15: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 19-02:15:39 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 19-02:15:39 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 20-02:29:35 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 20-02:29:35 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 20-02:29:35 (3767) [INFO] [0m
[32m* 20-02:29:36 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 20-02:29:36 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 20-02:29:36 (3777) [INFO]               : epel extras updates[0m
[32m* 20-02:29:36 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 20-02:29:36 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 20-02:29:36 (3787) [INFO] [0m
[32m* 20-02:29:36 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 20-02:29:36 (3767) [INFO] [0m
[32m* 20-02:29:36 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 20-02:29:37 (3777) [INFO] Determining fastest mirrors[0m
[32m* 20-02:29:43 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 20-02:29:43 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 20-02:29:43 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 20-02:29:43 (3777) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 20-02:29:43 (3777) [INFO]  * epel: mirror.yer.az[0m
[32m* 20-02:29:43 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 20-02:29:43 (3777) [INFO]  * updates: mirror.netdirekt.com.tr[0m
[32m* 20-02:31:19 (3777) [INFO] http://mirror.ni.net.tr/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.ni.net.tr/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')[0m
[32m* 20-02:31:19 (3777) [INFO] Trying other mirror.[0m
[32m* 20-02:31:35 (3777) [INFO] [0m
[32m* 20-02:31:35 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 20-02:31:35 (3787) [INFO] [0m
[33m* 20-02:31:35 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 20-02:31:35 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 20-02:31:36 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 20-02:31:36 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xxs4GoXIPk/ea_profile.json[0m
[32m* 20-02:31:43 (1619) [INFO] Backed up EA4 profile to /tmp/xxs4GoXIPk/ea_profile.json[0m
[33m* 20-02:31:43 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 20-02:31:45 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 20-02:31:46 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 21-02:15:15 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 21-02:15:15 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 21-02:15:15 (3767) [INFO] [0m
[32m* 21-02:15:15 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 21-02:15:15 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 21-02:15:15 (3777) [INFO]               : epel extras updates[0m
[32m* 21-02:15:15 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 21-02:15:16 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 21-02:15:16 (3787) [INFO] [0m
[32m* 21-02:15:16 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 21-02:15:16 (3767) [INFO] [0m
[32m* 21-02:15:16 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 21-02:15:16 (3777) [INFO] Determining fastest mirrors[0m
[32m* 21-02:15:21 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 21-02:15:21 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 21-02:15:21 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 21-02:15:21 (3777) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 21-02:15:21 (3777) [INFO]  * epel: mirror.yer.az[0m
[32m* 21-02:15:21 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 21-02:15:21 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 21-02:15:47 (3777) [INFO] [0m
[32m* 21-02:15:47 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 21-02:15:47 (3787) [INFO] [0m
[33m* 21-02:15:47 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 21-02:15:47 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 21-02:15:47 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 21-02:15:47 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/S0OmLQTlsS/ea_profile.json[0m
[32m* 21-02:15:50 (1619) [INFO] Backed up EA4 profile to /tmp/S0OmLQTlsS/ea_profile.json[0m
[33m* 21-02:15: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 21-02:15:51 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 21-02:15:51 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 22-02:19:09 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 22-02:19:09 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 22-02:19:09 (3767) [INFO] [0m
[32m* 22-02:19:09 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 22-02:19:09 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 22-02:19:09 (3777) [INFO]               : epel extras updates[0m
[32m* 22-02:19:10 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 22-02:19:10 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 22-02:19:10 (3787) [INFO] [0m
[32m* 22-02:19:10 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 22-02:19:10 (3767) [INFO] [0m
[32m* 22-02:19:11 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 22-02:19:11 (3777) [INFO] Determining fastest mirrors[0m
[32m* 22-02:19:20 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 22-02:19:20 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 22-02:19:20 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 22-02:19:20 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 22-02:19:20 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 22-02:19:20 (3777) [INFO]  * extras: mirror.netdirekt.com.tr[0m
[32m* 22-02:19:20 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 22-02:20:28 (3777) [INFO] [0m
[32m* 22-02:20:28 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 22-02:20:28 (3787) [INFO] [0m
[33m* 22-02:20:28 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 22-02:20:28 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 22-02:20:28 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 22-02:20:28 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hhac9XRvw8/ea_profile.json[0m
[32m* 22-02:20:29 (1619) [INFO] Backed up EA4 profile to /tmp/hhac9XRvw8/ea_profile.json[0m
[33m* 22-02:20:29 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 22-02:20:30 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 22-02:20:30 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 23-02:15:08 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 23-02:15:08 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 23-02:15:08 (3767) [INFO] [0m
[32m* 23-02:15:08 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 23-02:15:09 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 23-02:15:09 (3777) [INFO]               : epel extras updates[0m
[32m* 23-02:15:09 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 23-02:15:09 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 23-02:15:09 (3787) [INFO] [0m
[32m* 23-02:15:09 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 23-02:15:09 (3767) [INFO] [0m
[32m* 23-02:15:09 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 23-02:15:10 (3777) [INFO] Determining fastest mirrors[0m
[32m* 23-02:15:15 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 23-02:15:15 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 23-02:15:15 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 23-02:15:15 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 23-02:15:15 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 23-02:15:15 (3777) [INFO]  * extras: centos.vargonen.com[0m
[32m* 23-02:15:15 (3777) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 23-02:15:55 (3777) [INFO] [0m
[32m* 23-02:15:55 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 23-02:15:55 (3787) [INFO] [0m
[33m* 23-02:15:55 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 23-02:15:55 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 23-02:15:55 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 23-02:15:55 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5nxd_rTQpf/ea_profile.json[0m
[32m* 23-02:15:56 (1619) [INFO] Backed up EA4 profile to /tmp/5nxd_rTQpf/ea_profile.json[0m
[33m* 23-02:15: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 23-02:15:57 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 23-02:15:57 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 23-15:49:29 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 23-15:49:29 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 23-15:49:29 (3767) [INFO] [0m
[32m* 23-15:49:29 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 23-15:49:29 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 23-15:49:29 (3777) [INFO]               : epel extras updates[0m
[32m* 23-15:49:29 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 23-15:49:29 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 23-15:49:29 (3787) [INFO] [0m
[32m* 23-15:49:29 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 23-15:49:29 (3767) [INFO] [0m
[32m* 23-15:49:30 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 23-15:49:30 (3777) [INFO] Determining fastest mirrors[0m
[32m* 23-15:49:39 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 23-15:49:39 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 23-15:49:39 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 23-15:49:39 (3777) [INFO]  * base: mirror.alastyr.com[0m
[32m* 23-15:49:39 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 23-15:49:39 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 23-15:49:39 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 23-15:51:12 (3777) [INFO] https://mirrors.thzhost.com/epel/7/x86_64/repodata/d1f2db5c83464601d725a725b232936d8771a3c316bd60bec3e771f3961563c1-primary.sqlite.bz2: [Errno 12] Timeout on https://mirrors.thzhost.com/epel/7/x86_64/repodata/d1f2db5c83464601d725a725b232936d8771a3c316bd60bec3e771f3961563c1-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')[0m
[32m* 23-15:51:12 (3777) [INFO] Trying other mirror.[0m
[32m* 23-15:51:31 (3777) [INFO] [0m
[32m* 23-15:51:31 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 23-15:51:31 (3787) [INFO] [0m
[33m* 23-15:51:31 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 23-15:51:31 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 23-15:51:32 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 23-15:51:32 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_JHp0_f_qf/ea_profile.json[0m
[32m* 23-15:51:34 (1619) [INFO] Backed up EA4 profile to /tmp/_JHp0_f_qf/ea_profile.json[0m
[33m* 23-15:51:34 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 23-15:51:34 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 23-15:51:34 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 24-02:15:33 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 24-02:15:33 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 24-02:15:33 (3767) [INFO] [0m
[32m* 24-02:15:34 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 24-02:15:34 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 24-02:15:34 (3777) [INFO]               : epel extras updates[0m
[32m* 24-02:15:34 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 24-02:15:34 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 24-02:15:34 (3787) [INFO] [0m
[32m* 24-02:15:34 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 24-02:15:34 (3767) [INFO] [0m
[32m* 24-02:15:34 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 24-02:15:35 (3777) [INFO] Determining fastest mirrors[0m
[32m* 24-02:15:44 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 24-02:15:44 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 24-02:15:44 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 24-02:15:44 (3777) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 24-02:15:44 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 24-02:15:44 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 24-02:15:44 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 24-02:16:10 (3777) [INFO] [0m
[32m* 24-02:16:10 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 24-02:16:10 (3787) [INFO] [0m
[33m* 24-02:16:10 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 24-02:16:10 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 24-02:16:10 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 24-02:16:10 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gtuWqWvzKp/ea_profile.json[0m
[32m* 24-02:16:12 (1619) [INFO] Backed up EA4 profile to /tmp/gtuWqWvzKp/ea_profile.json[0m
[33m* 24-02:16: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 24-02:16:13 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 24-02:16:13 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 25-02:18:37 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 25-02:18:38 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 25-02:18:38 (3767) [INFO] [0m
[32m* 25-02:18:38 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 25-02:18:38 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 25-02:18:38 (3777) [INFO]               : epel extras updates[0m
[32m* 25-02:18:38 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 25-02:18:38 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 25-02:18:38 (3787) [INFO] [0m
[32m* 25-02:18:38 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 25-02:18:38 (3767) [INFO] [0m
[32m* 25-02:18:39 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 25-02:18:39 (3777) [INFO] Determining fastest mirrors[0m
[32m* 25-02:18:46 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 25-02:18:46 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 25-02:18:46 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 25-02:18:46 (3777) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 25-02:18:46 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 25-02:18:46 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 25-02:18:46 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 25-02:19:23 (3777) [INFO] [0m
[32m* 25-02:19:23 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 25-02:19:23 (3787) [INFO] [0m
[33m* 25-02:19:23 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 25-02:19:23 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 25-02:19:23 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 25-02:19:23 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_FLTBYiMwe/ea_profile.json[0m
[32m* 25-02:19:25 (1619) [INFO] Backed up EA4 profile to /tmp/_FLTBYiMwe/ea_profile.json[0m
[33m* 25-02:19:25 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 25-02:19:26 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 25-02:19:26 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 26-02:15:10 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 26-02:15:11 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 26-02:15:11 (3767) [INFO] [0m
[32m* 26-02:15:12 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 26-02:15:13 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 26-02:15:13 (3777) [INFO]               : epel extras updates[0m
[32m* 26-02:15:13 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 26-02:15:13 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 26-02:15:13 (3787) [INFO] [0m
[32m* 26-02:15:13 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 26-02:15:13 (3767) [INFO] [0m
[32m* 26-02:15:13 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 26-02:15:14 (3777) [INFO] Determining fastest mirrors[0m
[32m* 26-02:15:23 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 26-02:15:23 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 26-02:15:23 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 26-02:15:23 (3777) [INFO]  * base: mirror.alastyr.com[0m
[32m* 26-02:15:23 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 26-02:15:23 (3777) [INFO]  * extras: mirror.alastyr.com[0m
[32m* 26-02:15:23 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 26-02:16:01 (3777) [INFO] [0m
[32m* 26-02:16:01 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 26-02:16:02 (3787) [INFO] [0m
[33m* 26-02:16:02 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 26-02:16:02 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 26-02:16:02 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 26-02:16:02 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/E39GEUVaTg/ea_profile.json[0m
[32m* 26-02:16:03 (1619) [INFO] Backed up EA4 profile to /tmp/E39GEUVaTg/ea_profile.json[0m
[33m* 26-02:16:03 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 26-02:16:04 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 26-02:16:04 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 27-02:15:35 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 27-02:15:35 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 27-02:15:35 (3767) [INFO] [0m
[32m* 27-02:15:35 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 27-02:15:35 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 27-02:15:35 (3777) [INFO]               : epel extras updates[0m
[32m* 27-02:15:36 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 27-02:15:36 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 27-02:15:36 (3787) [INFO] [0m
[32m* 27-02:15:36 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 27-02:15:36 (3767) [INFO] [0m
[32m* 27-02:15:36 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 27-02:15:37 (3777) [INFO] Determining fastest mirrors[0m
[32m* 27-02:15:44 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 27-02:15:44 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 27-02:15:44 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 27-02:15:44 (3777) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 27-02:15:44 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 27-02:15:44 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 27-02:15:44 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 27-02:16:35 (3777) [INFO] [0m
[32m* 27-02:16:35 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 27-02:16:36 (3787) [INFO] [0m
[33m* 27-02:16:36 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 27-02:16:36 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 27-02:16:36 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 27-02:16:36 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MRSlIYjIq9/ea_profile.json[0m
[32m* 27-02:16:40 (1619) [INFO] Backed up EA4 profile to /tmp/MRSlIYjIq9/ea_profile.json[0m
[33m* 27-02:16: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 27-02:16:41 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 27-02:16:41 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 28-02:16:56 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 28-02:16:56 (3473) [ERROR] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/b3bbf62f1ee6634e6a2208e557643c8181b623de79e2101052c1bc5714e58dc8-other.sqlite.bz2: [Errno 12] Timeout on https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/b3bbf62f1ee6634e6a2208e557643c8181b623de79e2101052c1bc5714e58dc8-other.sqlite.bz2: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
Trying other mirror.
[0m
[33m* 28-02:16:56 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[33m* 28-02:17:03 (2667) [WARN] *** Elevation Blocker detected: ***
disk space issue
[0m
[32m* 28-02:17:03 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 28-02:17:03 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 28-02:17:03 (3767) [INFO] [0m
[32m* 28-02:17:05 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 28-02:17:06 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 28-02:17:06 (3777) [INFO]               : epel extras updates[0m
[32m* 28-02:17:07 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 28-02:17:07 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 28-02:17:07 (3787) [INFO] [0m
[32m* 28-02:17:07 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 28-02:17:07 (3767) [INFO] [0m
[32m* 28-02:17:13 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 28-02:17:16 (3777) [INFO] Determining fastest mirrors[0m
[32m* 28-02:17:22 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 28-02:17:22 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 28-02:17:22 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 28-02:17:22 (3777) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 28-02:17:22 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 28-02:17:22 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 28-02:17:22 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 28-02:17:59 (3777) [INFO] [0m
[32m* 28-02:17:59 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 28-02:17:59 (3787) [INFO] [0m
[33m* 28-02:17:59 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 28-02:17:59 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 28-02:17:59 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 28-02:17:59 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/N0ykWl0x_J/ea_profile.json[0m
[32m* 28-02:18:01 (1619) [INFO] Backed up EA4 profile to /tmp/N0ykWl0x_J/ea_profile.json[0m
[33m* 28-02:18: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 28-02:18:02 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 28-02:18:02 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 29-02:14:01 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 29-02:14:03 (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 30001 milliseconds with 0 out of 0 bytes received')
[0m
[33m* 29-02:14:03 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 29-02:14:04 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 29-02:14:04 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 29-02:14:04 (3767) [INFO] [0m
[32m* 29-02:14:04 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 29-02:14:04 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 29-02:14:04 (3777) [INFO]               : epel extras updates[0m
[32m* 29-02:14:04 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 29-02:14:04 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 29-02:14:04 (3787) [INFO] [0m
[32m* 29-02:14:04 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 29-02:14:04 (3767) [INFO] [0m
[32m* 29-02:14:05 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 29-02:14:05 (3777) [INFO] Determining fastest mirrors[0m
[32m* 29-02:14:15 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 29-02:14:15 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 29-02:14:15 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 29-02:14:15 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 29-02:14:15 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 29-02:14:15 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 29-02:14:15 (3777) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 29-02:14:53 (3777) [INFO] [0m
[32m* 29-02:14:53 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 29-02:14:53 (3787) [INFO] [0m
[33m* 29-02:14:53 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 29-02:14:53 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 29-02:14:53 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 29-02:14:53 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ejoP864R9b/ea_profile.json[0m
[32m* 29-02:14:55 (1619) [INFO] Backed up EA4 profile to /tmp/ejoP864R9b/ea_profile.json[0m
[33m* 29-02:14: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 29-02:14:56 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 29-02:14:56 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 30-02:13:54 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 30-02:13:54 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 30-02:13:54 (3767) [INFO] [0m
[32m* 30-02:13:54 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 30-02:13:55 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 30-02:13:55 (3777) [INFO]               : epel extras updates[0m
[32m* 30-02:13:55 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 30-02:13:55 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 30-02:13:55 (3787) [INFO] [0m
[32m* 30-02:13:55 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 30-02:13:55 (3767) [INFO] [0m
[32m* 30-02:13:55 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 30-02:13:56 (3777) [INFO] Determining fastest mirrors[0m
[32m* 30-02:14:06 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 30-02:14:06 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 30-02:14:06 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 30-02:14:06 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 30-02:14:06 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 30-02:14:06 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 30-02:14:06 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 30-02:14:20 (3777) [INFO] http://centos.vargonen.com/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"[0m
[32m* 30-02:14:20 (3777) [INFO] Trying other mirror.[0m
[32m* 30-02:14:40 (3777) [INFO] [0m
[32m* 30-02:14:40 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 30-02:14:40 (3787) [INFO] [0m
[33m* 30-02:14:40 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 30-02:14:40 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 30-02:14:40 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 30-02:14:40 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/STaAFXJWbf/ea_profile.json[0m
[32m* 30-02:14:43 (1619) [INFO] Backed up EA4 profile to /tmp/STaAFXJWbf/ea_profile.json[0m
[33m* 30-02:14:43 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 30-02:14:44 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 30-02:14:45 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 30-15:52:40 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 30-15:52:40 (3473) [ERROR] http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/01e51a9bb92caff59dc3f14ada438577e6d7312a3c29ef14d4f92ccaed5dc793-other.sqlite.bz2: [Errno 12] Timeout on http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/01e51a9bb92caff59dc3f14ada438577e6d7312a3c29ef14d4f92ccaed5dc793-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/01e51a9bb92caff59dc3f14ada438577e6d7312a3c29ef14d4f92ccaed5dc793-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://mirror.natro.com/centos/7.9.2009/updates/x86_64/repodata/de655a1791702b3522d4ab79d385a605d016c8d60b0f0e5e1149438dbf51726c-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.natro.com/centos/7.9.2009/updates/x86_64/repodata/de655a1791702b3522d4ab79d385a605d016c8d60b0f0e5e1149438dbf51726c-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirror.natro.com/centos/7.9.2009/extras/x86_64/repodata/78c0e5530bc46d128e18eca9ff16b2d0651efdb33434408f8ff1db4d14f1bb99-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.natro.com/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.
[0m
[33m* 30-15:52:40 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 30-15:52:41 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 30-15:52:41 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 30-15:52:41 (3767) [INFO] [0m
[32m* 30-15:52:41 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 30-15:52:41 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 30-15:52:41 (3777) [INFO]               : epel extras updates[0m
[32m* 30-15:52:41 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 30-15:52:41 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 30-15:52:41 (3787) [INFO] [0m
[32m* 30-15:52:41 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 30-15:52:41 (3767) [INFO] [0m
[32m* 30-15:52:42 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 30-15:52:42 (3777) [INFO] Determining fastest mirrors[0m
[32m* 30-15:52:52 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 30-15:52:52 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 30-15:52:52 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 30-15:52:52 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 30-15:52:52 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 30-15:52:52 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 30-15:52:52 (3777) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 30-15:53:44 (3777) [INFO] http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/23f724f91a8a452bc8153a36fe82fcde010af6255e3943b6ec96719ff9fb64b5-primary.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/23f724f91a8a452bc8153a36fe82fcde010af6255e3943b6ec96719ff9fb64b5-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')[0m
[32m* 30-15:53:44 (3777) [INFO] Trying other mirror.[0m
[32m* 30-15:53:45 (3777) [INFO] http://mirror.radoreservers.com/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.radoreservers.com/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')[0m
[32m* 30-15:53:45 (3777) [INFO] Trying other mirror.[0m
[32m* 30-15:53:47 (3777) [INFO] http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/23f724f91a8a452bc8153a36fe82fcde010af6255e3943b6ec96719ff9fb64b5-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum[0m
[32m* 30-15:53:47 (3777) [INFO] Trying other mirror.[0m
[32m* 30-15:54:04 (3777) [INFO] http://mirror.alastyr.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.alastyr.com/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')[0m
[32m* 30-15:54:04 (3777) [INFO] Trying other mirror.[0m
[32m* 30-15:54:31 (3777) [INFO] https://hkg.mirror.rackspace.com/epel/7/x86_64/repodata/a82d9bdbfaef270a4ae31c8377e6a366562b1c2f38f015e15a432314166dbc7e-primary.sqlite.bz2: [Errno 12] Timeout on https://hkg.mirror.rackspace.com/epel/7/x86_64/repodata/a82d9bdbfaef270a4ae31c8377e6a366562b1c2f38f015e15a432314166dbc7e-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')[0m
[32m* 30-15:54:31 (3777) [INFO] Trying other mirror.[0m
[32m* 30-15:54:47 (3777) [INFO] [0m
[32m* 30-15:54:47 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 30-15:54:47 (3787) [INFO] [0m
[33m* 30-15:54:47 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 30-15:54:47 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 30-15:54:52 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 30-15:54:52 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rH9i9mVx1G/ea_profile.json[0m
[32m* 30-15:54:53 (1619) [INFO] Backed up EA4 profile to /tmp/rH9i9mVx1G/ea_profile.json[0m
[33m* 30-15:54:53 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 30-15:54:54 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 30-15:54:54 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 31-02:17:56 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 31-02:17:56 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 31-02:17:56 (3767) [INFO] [0m
[32m* 31-02:17:57 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 31-02:17:57 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 31-02:17:57 (3777) [INFO]               : epel extras updates[0m
[32m* 31-02:17:57 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 31-02:17:57 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 31-02:17:57 (3787) [INFO] [0m
[32m* 31-02:17:57 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 31-02:17:57 (3767) [INFO] [0m
[32m* 31-02:17:58 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 31-02:18:00 (3777) [INFO] Determining fastest mirrors[0m
[32m* 31-02:18:09 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 31-02:18:09 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 31-02:18:09 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 31-02:18:09 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 31-02:18:09 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 31-02:18:09 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 31-02:18:09 (3777) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 31-02:19:22 (3777) [INFO] [0m
[32m* 31-02:19:22 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 31-02:19:23 (3787) [INFO] [0m
[33m* 31-02:19:23 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 31-02:19:23 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 31-02:19:23 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 31-02:19:24 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1yJ4n85mwj/ea_profile.json[0m
[32m* 31-02:19:31 (1619) [INFO] Backed up EA4 profile to /tmp/1yJ4n85mwj/ea_profile.json[0m
[33m* 31-02:19:31 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 31-02:19:33 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 31-02:19:33 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 01-02:16:27 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 01-02:16:27 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 01-02:16:27 (3767) [INFO] [0m
[32m* 01-02:16:27 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 01-02:16:28 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 01-02:16:28 (3777) [INFO]               : epel extras updates[0m
[32m* 01-02:16:28 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 01-02:16:28 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 01-02:16:28 (3787) [INFO] [0m
[32m* 01-02:16:28 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 01-02:16:28 (3767) [INFO] [0m
[32m* 01-02:16:28 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 01-02:16:29 (3777) [INFO] Determining fastest mirrors[0m
[32m* 01-02:16:33 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 01-02:16:33 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 01-02:16:33 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 01-02:16:33 (3777) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 01-02:16:33 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 01-02:16:33 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 01-02:16:33 (3777) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 01-02:17:05 (3777) [INFO] [0m
[32m* 01-02:17:05 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 01-02:17:05 (3787) [INFO] [0m
[33m* 01-02:17:05 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 01-02:17:05 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 01-02:17:05 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 01-02:17:05 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PEaJ4zmhgN/ea_profile.json[0m
[32m* 01-02:17:07 (1619) [INFO] Backed up EA4 profile to /tmp/PEaJ4zmhgN/ea_profile.json[0m
[33m* 01-02:17:07 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 01-02:17:08 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 01-02:17:09 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 02-02:16:08 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 02-02:16:08 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 02-02:16:08 (3767) [INFO] [0m
[32m* 02-02:16:08 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 02-02:16:08 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 02-02:16:08 (3777) [INFO]               : epel extras updates[0m
[32m* 02-02:16:08 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 02-02:16:08 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 02-02:16:08 (3787) [INFO] [0m
[32m* 02-02:16:08 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 02-02:16:08 (3767) [INFO] [0m
[32m* 02-02:16:09 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 02-02:16:09 (3777) [INFO] Determining fastest mirrors[0m
[32m* 02-02:16:15 (3777) [INFO]  * EA4: 185.157.208.252[0m
[32m* 02-02:16:15 (3777) [INFO]  * cpanel-addons-production-feed: 185.157.208.252[0m
[32m* 02-02:16:15 (3777) [INFO]  * cpanel-plugins: 185.157.208.252[0m
[32m* 02-02:16:15 (3777) [INFO]  * base: kozyatagi.mirror.guzel.net.tr[0m
[32m* 02-02:16:15 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 02-02:16:15 (3777) [INFO]  * extras: mirror.alastyr.com[0m
[32m* 02-02:16:15 (3777) [INFO]  * updates: mirror.alastyr.com[0m
[32m* 02-02:16:44 (3777) [INFO] [0m
[32m* 02-02:16:44 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 02-02:16:44 (3787) [INFO] [0m
[33m* 02-02:16:45 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 02-02:16:45 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 02-02:16:45 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 02-02:16:45 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/19_YixUdgC/ea_profile.json[0m
[32m* 02-02:16:49 (1619) [INFO] Backed up EA4 profile to /tmp/19_YixUdgC/ea_profile.json[0m
[33m* 02-02:16:49 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 02-02:16:50 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 02-02:16:51 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 03-02:15:03 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 03-02:15:03 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 03-02:15:03 (3767) [INFO] [0m
[32m* 03-02:15:03 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 03-02:15:03 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 03-02:15:03 (3777) [INFO]               : epel extras updates[0m
[32m* 03-02:15:05 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 03-02:15:05 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 03-02:15:05 (3787) [INFO] [0m
[32m* 03-02:15:05 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 03-02:15:05 (3767) [INFO] [0m
[32m* 03-02:15:05 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 03-02:15:06 (3777) [INFO] Determining fastest mirrors[0m
[32m* 03-02:15:15 (3777) [INFO]  * EA4: 185.157.208.252[0m
[32m* 03-02:15:15 (3777) [INFO]  * cpanel-addons-production-feed: 185.157.208.252[0m
[32m* 03-02:15:15 (3777) [INFO]  * cpanel-plugins: 185.157.208.252[0m
[32m* 03-02:15:15 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 03-02:15:15 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 03-02:15:15 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 03-02:15:15 (3777) [INFO]  * updates: kozyatagi.mirror.guzel.net.tr[0m
[32m* 03-02:16:22 (3777) [INFO] [0m
[32m* 03-02:16:22 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 03-02:16:22 (3787) [INFO] [0m
[33m* 03-02:16:22 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 03-02:16:22 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 03-02:16:22 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 03-02:16:22 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hrkPKYzKOh/ea_profile.json[0m
[32m* 03-02:16:25 (1619) [INFO] Backed up EA4 profile to /tmp/hrkPKYzKOh/ea_profile.json[0m
[33m* 03-02:16:25 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 03-02:16:26 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 03-02:16:26 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 04-02:14:01 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 04-02:14:02 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 04-02:14:02 (3767) [INFO] [0m
[32m* 04-02:14:02 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 04-02:14:02 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 04-02:14:02 (3777) [INFO]               : epel extras updates[0m
[32m* 04-02:14:03 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 04-02:14:03 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 04-02:14:03 (3787) [INFO] [0m
[32m* 04-02:14:03 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 04-02:14:03 (3767) [INFO] [0m
[32m* 04-02:14:03 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 04-02:14:04 (3777) [INFO] Determining fastest mirrors[0m
[32m* 04-02:14:16 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 04-02:14:16 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 04-02:14:16 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 04-02:14:16 (3777) [INFO]  * base: mirror.alastyr.com[0m
[32m* 04-02:14:16 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 04-02:14:16 (3777) [INFO]  * extras: kozyatagi.mirror.guzel.net.tr[0m
[32m* 04-02:14:16 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 04-02:14:53 (3777) [INFO] [0m
[32m* 04-02:14:53 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 04-02:14:53 (3787) [INFO] [0m
[33m* 04-02:14:53 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 04-02:14:53 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 04-02:14:53 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 04-02:14:53 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4tU1i7WD5j/ea_profile.json[0m
[32m* 04-02:14:55 (1619) [INFO] Backed up EA4 profile to /tmp/4tU1i7WD5j/ea_profile.json[0m
[33m* 04-02:14: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 04-02:14:56 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 04-02:14:56 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 05-02:21:25 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 05-02:21:25 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 05-02:21:25 (3767) [INFO] [0m
[32m* 05-02:21:25 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 05-02:21:25 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 05-02:21:25 (3777) [INFO]               : epel extras updates[0m
[32m* 05-02:21:25 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 05-02:21:25 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 05-02:21:25 (3787) [INFO] [0m
[32m* 05-02:21:25 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 05-02:21:25 (3767) [INFO] [0m
[32m* 05-02:21:26 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 05-02:21:26 (3777) [INFO] Determining fastest mirrors[0m
[32m* 05-02:21:43 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 05-02:21:43 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 05-02:21:43 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 05-02:21:43 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 05-02:21:43 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 05-02:21:43 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 05-02:21:43 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 05-02:22:31 (3777) [INFO] [0m
[32m* 05-02:22:31 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 05-02:22:31 (3787) [INFO] [0m
[33m* 05-02:22:31 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 05-02:22:31 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 05-02:22:31 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 05-02:22:31 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/i7kJfR6f5V/ea_profile.json[0m
[32m* 05-02:22:32 (1619) [INFO] Backed up EA4 profile to /tmp/i7kJfR6f5V/ea_profile.json[0m
[33m* 05-02:22:32 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 05-02:22:33 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 05-02:22:33 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 06-02:16:58 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 06-02:16:58 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 06-02:16:58 (3767) [INFO] [0m
[32m* 06-02:16:58 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 06-02:16:58 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 06-02:16:58 (3777) [INFO]               : epel extras updates[0m
[32m* 06-02:16:58 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 06-02:16:58 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 06-02:16:58 (3787) [INFO] [0m
[32m* 06-02:16:58 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 06-02:16:58 (3767) [INFO] [0m
[32m* 06-02:16:59 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 06-02:16:59 (3777) [INFO] Determining fastest mirrors[0m
[32m* 06-02:17:06 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 06-02:17:06 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 06-02:17:06 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 06-02:17:06 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 06-02:17:06 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 06-02:17:06 (3777) [INFO]  * extras: centos.vargonen.com[0m
[32m* 06-02:17:06 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 06-02:18:44 (3777) [INFO] https://mirror.sabay.com.kh/epel/7/x86_64/repodata/6792903c696639d9ac3cf2604a34311f05a8824e72cfcd28cdab31693b262c79-primary.sqlite.bz2: [Errno 12] Timeout on https://mirror.sabay.com.kh/epel/7/x86_64/repodata/6792903c696639d9ac3cf2604a34311f05a8824e72cfcd28cdab31693b262c79-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')[0m
[32m* 06-02:18:44 (3777) [INFO] Trying other mirror.[0m
[32m* 06-02:19:05 (3777) [INFO] [0m
[32m* 06-02:19:05 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 06-02:19:05 (3787) [INFO] [0m
[33m* 06-02:19:05 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 06-02:19:05 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 06-02:19:05 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 06-02:19:05 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cwBL0RlP4d/ea_profile.json[0m
[32m* 06-02:19:06 (1619) [INFO] Backed up EA4 profile to /tmp/cwBL0RlP4d/ea_profile.json[0m
[33m* 06-02:19: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 06-02:19:07 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 06-02:19:07 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 06-15:52:16 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 06-15:52:16 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 06-15:52:16 (3767) [INFO] [0m
[32m* 06-15:52:16 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 06-15:52:16 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 06-15:52:16 (3777) [INFO]               : epel extras updates[0m
[32m* 06-15:52:16 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 06-15:52:16 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 06-15:52:17 (3787) [INFO] [0m
[32m* 06-15:52:17 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 06-15:52:17 (3767) [INFO] [0m
[32m* 06-15:52:17 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 06-15:52:17 (3777) [INFO] Determining fastest mirrors[0m
[32m* 06-15:52:26 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 06-15:52:26 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 06-15:52:26 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 06-15:52:26 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 06-15:52:26 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 06-15:52:26 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 06-15:52:26 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 06-15:53:08 (3777) [INFO] [0m
[32m* 06-15:53:08 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 06-15:53:08 (3787) [INFO] [0m
[33m* 06-15:53:08 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 06-15:53:08 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 06-15:53:08 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 06-15:53:08 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QA7f8D90Ni/ea_profile.json[0m
[32m* 06-15:53:09 (1619) [INFO] Backed up EA4 profile to /tmp/QA7f8D90Ni/ea_profile.json[0m
[33m* 06-15:53: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 06-15:53:10 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 06-15:53:10 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 07-02:14:59 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 07-02:14:59 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 07-02:14:59 (3767) [INFO] [0m
[32m* 07-02:14:59 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 07-02:14:59 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 07-02:14:59 (3777) [INFO]               : epel extras updates[0m
[32m* 07-02:14:59 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 07-02:14:59 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 07-02:14:59 (3787) [INFO] [0m
[32m* 07-02:14:59 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 07-02:14:59 (3767) [INFO] [0m
[32m* 07-02:15:00 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 07-02:15:00 (3777) [INFO] Determining fastest mirrors[0m
[32m* 07-02:15:07 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 07-02:15:07 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 07-02:15:07 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 07-02:15:07 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 07-02:15:07 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 07-02:15:07 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 07-02:15:07 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 07-02:15:32 (3777) [INFO] [0m
[32m* 07-02:15:32 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 07-02:15:32 (3787) [INFO] [0m
[33m* 07-02:15:32 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 07-02:15:32 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 07-02:15:32 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 07-02:15:32 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aSLph3kce8/ea_profile.json[0m
[32m* 07-02:15:34 (1619) [INFO] Backed up EA4 profile to /tmp/aSLph3kce8/ea_profile.json[0m
[33m* 07-02:15:34 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 07-02:15:35 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 07-02:15:35 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 08-02:15:38 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 08-02:15:39 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 08-02:15:39 (3767) [INFO] [0m
[32m* 08-02:15:39 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 08-02:15:39 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 08-02:15:39 (3777) [INFO]               : epel extras updates[0m
[32m* 08-02:15:40 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 08-02:15:40 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 08-02:15:40 (3787) [INFO] [0m
[32m* 08-02:15:40 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 08-02:15:40 (3767) [INFO] [0m
[32m* 08-02:15:40 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 08-02:15:41 (3777) [INFO] Determining fastest mirrors[0m
[32m* 08-02:15:48 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 08-02:15:48 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 08-02:15:48 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 08-02:15:48 (3777) [INFO]  * base: ftp.linux.org.tr[0m
[32m* 08-02:15:48 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 08-02:15:48 (3777) [INFO]  * extras: mirror.alastyr.com[0m
[32m* 08-02:15:48 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 08-02:17:40 (3777) [INFO] https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/a8441835239fb58a12d472659f37e31e4b0e60d7ac3a5ed8e9bfcea1f4b77e91-primary.sqlite.bz2: [Errno 12] Timeout on https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/a8441835239fb58a12d472659f37e31e4b0e60d7ac3a5ed8e9bfcea1f4b77e91-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')[0m
[32m* 08-02:17:40 (3777) [INFO] Trying other mirror.[0m
[32m* 08-02:17:58 (3777) [INFO] [0m
[32m* 08-02:17:58 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 08-02:17:58 (3787) [INFO] [0m
[33m* 08-02:17:58 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 08-02:17:58 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 08-02:17:58 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 08-02:17:58 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LxuBAlo11a/ea_profile.json[0m
[32m* 08-02:18:00 (1619) [INFO] Backed up EA4 profile to /tmp/LxuBAlo11a/ea_profile.json[0m
[33m* 08-02:18:00 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 08-02:18:01 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 08-02:18:01 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 09-02:17:18 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 09-02:17:18 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 09-02:17:18 (3767) [INFO] [0m
[32m* 09-02:17:18 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 09-02:17:18 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 09-02:17:18 (3777) [INFO]               : epel extras updates[0m
[32m* 09-02:17:18 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 09-02:17:18 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 09-02:17:18 (3787) [INFO] [0m
[32m* 09-02:17:18 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 09-02:17:18 (3767) [INFO] [0m
[32m* 09-02:17:18 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 09-02:17:19 (3777) [INFO] Determining fastest mirrors[0m
[32m* 09-02:17:28 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 09-02:17:28 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 09-02:17:28 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 09-02:17:28 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 09-02:17:28 (3777) [INFO]  * epel: mirror.yer.az[0m
[32m* 09-02:17:28 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 09-02:17:28 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 09-02:17:49 (3777) [INFO] [0m
[32m* 09-02:17:49 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 09-02:17:49 (3787) [INFO] [0m
[33m* 09-02:17:49 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 09-02:17:49 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 09-02:17:49 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 09-02:17:49 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tDuvdqXyo6/ea_profile.json[0m
[32m* 09-02:17:51 (1619) [INFO] Backed up EA4 profile to /tmp/tDuvdqXyo6/ea_profile.json[0m
[33m* 09-02:17:51 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 09-02:17:52 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 09-02:17:52 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 10-02:15:33 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 10-02:15:33 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 10-02:15:33 (3767) [INFO] [0m
[32m* 10-02:15:34 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 10-02:15:34 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 10-02:15:34 (3777) [INFO]               : epel extras updates[0m
[32m* 10-02:15:34 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 10-02:15:34 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 10-02:15:34 (3787) [INFO] [0m
[32m* 10-02:15:34 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 10-02:15:34 (3767) [INFO] [0m
[32m* 10-02:15:34 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 10-02:15:35 (3777) [INFO] Determining fastest mirrors[0m
[32m* 10-02:15:57 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 10-02:15:57 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 10-02:15:57 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 10-02:15:57 (3777) [INFO]  * base: mirror.radoreservers.com[0m
[32m* 10-02:15:57 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 10-02:15:57 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 10-02:15:57 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 10-02:16:28 (3777) [INFO] [0m
[32m* 10-02:16:28 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 10-02:16:28 (3787) [INFO] [0m
[33m* 10-02:16:28 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 10-02:16:28 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 10-02:16:28 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 10-02:16:28 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/CcM1lwZtOh/ea_profile.json[0m
[32m* 10-02:16:31 (1619) [INFO] Backed up EA4 profile to /tmp/CcM1lwZtOh/ea_profile.json[0m
[33m* 10-02:16:31 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 10-02:16:31 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 10-02:16:32 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 11-02:21:06 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 11-02:21:06 (3473) [ERROR] http://centos.vargonen.com/centos/7.9.2009/extras/x86_64/repodata/78c0e5530bc46d128e18eca9ff16b2d0651efdb33434408f8ff1db4d14f1bb99-other.sqlite.bz2: [Errno 12] Timeout on http://centos.vargonen.com/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.
https://mirror.yer.az/fedora-epel/7/x86_64/repodata/65f4952ebe7a422d1db811c3dbf62a9099043c358a9a5b74a6f994968771b595-other.sqlite.bz2: [Errno 12] Timeout on https://mirror.yer.az/fedora-epel/7/x86_64/repodata/65f4952ebe7a422d1db811c3dbf62a9099043c358a9a5b74a6f994968771b595-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirror.netdirekt.com.tr/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.netdirekt.com.tr/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.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/65f4952ebe7a422d1db811c3dbf62a9099043c358a9a5b74a6f994968771b595-other.sqlite.bz2: [Errno 12] Timeout on http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/65f4952ebe7a422d1db811c3dbf62a9099043c358a9a5b74a6f994968771b595-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/65f4952ebe7a422d1db811c3dbf62a9099043c358a9a5b74a6f994968771b595-other.sqlite.bz2: [Errno 12] Timeout on https://repo.extreme-ix.org/epel/7/x86_64/repodata/65f4952ebe7a422d1db811c3dbf62a9099043c358a9a5b74a6f994968771b595-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://hkg.mirror.rackspace.com/epel/7/x86_64/repodata/65f4952ebe7a422d1db811c3dbf62a9099043c358a9a5b74a6f994968771b595-other.sqlite.bz2: [Errno 12] Timeout on https://hkg.mirror.rackspace.com/epel/7/x86_64/repodata/65f4952ebe7a422d1db811c3dbf62a9099043c358a9a5b74a6f994968771b595-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror-jp.misakamikoto.network/fedora-epel/7/x86_64/repodata/65f4952ebe7a422d1db811c3dbf62a9099043c358a9a5b74a6f994968771b595-other.sqlite.bz2: [Errno 12] Timeout on https://mirror-jp.misakamikoto.network/fedora-epel/7/x86_64/repodata/65f4952ebe7a422d1db811c3dbf62a9099043c358a9a5b74a6f994968771b595-other.sqlite.bz2: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
Trying other mirror.
http://mirrors.nipa.cloud/epel/7/x86_64/repodata/65f4952ebe7a422d1db811c3dbf62a9099043c358a9a5b74a6f994968771b595-other.sqlite.bz2: [Errno 12] Timeout on http://mirrors.nipa.cloud/epel/7/x86_64/repodata/65f4952ebe7a422d1db811c3dbf62a9099043c358a9a5b74a6f994968771b595-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
[0m
[33m* 11-02:21:06 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 11-02:21:07 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 11-02:21:07 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 11-02:21:07 (3767) [INFO] [0m
[32m* 11-02:21:07 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 11-02:21:08 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 11-02:21:08 (3777) [INFO]               : epel extras updates[0m
[32m* 11-02:21:08 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 11-02:21:08 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 11-02:21:08 (3787) [INFO] [0m
[32m* 11-02:21:08 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 11-02:21:08 (3767) [INFO] [0m
[32m* 11-02:21:08 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 11-02:21:09 (3777) [INFO] Determining fastest mirrors[0m
[32m* 11-02:21:41 (3777) [INFO]  * EA4: 185.157.208.252[0m
[32m* 11-02:21:41 (3777) [INFO]  * cpanel-addons-production-feed: 185.157.208.252[0m
[32m* 11-02:21:41 (3777) [INFO]  * cpanel-plugins: 185.157.208.252[0m
[32m* 11-02:21:41 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 11-02:21:41 (3777) [INFO]  * epel: mirror.yer.az[0m
[32m* 11-02:21:41 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 11-02:21:41 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 11-02:22:07 (3777) [INFO] http://178.18.193.52/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/f0c0f842237bc5eaca73ff553bfdeb6b7920420066150151b48e085a2ec2362e-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"[0m
[32m* 11-02:22:07 (3777) [INFO] Trying other mirror.[0m
[32m* 11-02:22:36 (3777) [INFO] https://mirror.yer.az/fedora-epel/7/x86_64/repodata/5db6f8ed3235709d55eacd6f5e8df08beee6c74f691660b63f7a737d11d4c96a-comps-Everything.x86_64.xml.gz: [Errno 12] Timeout on https://mirror.yer.az/fedora-epel/7/x86_64/repodata/5db6f8ed3235709d55eacd6f5e8df08beee6c74f691660b63f7a737d11d4c96a-comps-Everything.x86_64.xml.gz: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')[0m
[32m* 11-02:22:36 (3777) [INFO] Trying other mirror.[0m
[32m* 11-02:22:41 (3777) [INFO] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/7a5574a1e3cdbef170c0315d92d961509411fce09356e652ff788cf3cf7f4981-primary.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/7a5574a1e3cdbef170c0315d92d961509411fce09356e652ff788cf3cf7f4981-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')[0m
[32m* 11-02:22:41 (3777) [INFO] Trying other mirror.[0m
[32m* 11-02:23:07 (3777) [INFO] https://mirror.yer.az/fedora-epel/7/x86_64/repodata/cfc073a5f5b3c2da8386a18d63cdb1975216bdca8a8005ea9dcdbcce01cdc246-updateinfo.xml.bz2: [Errno 12] Timeout on https://mirror.yer.az/fedora-epel/7/x86_64/repodata/cfc073a5f5b3c2da8386a18d63cdb1975216bdca8a8005ea9dcdbcce01cdc246-updateinfo.xml.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')[0m
[32m* 11-02:23:07 (3777) [INFO] Trying other mirror.[0m
[32m* 11-02:23:11 (3777) [INFO] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/5db6f8ed3235709d55eacd6f5e8df08beee6c74f691660b63f7a737d11d4c96a-comps-Everything.x86_64.xml.gz: [Errno 12] Timeout on https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/5db6f8ed3235709d55eacd6f5e8df08beee6c74f691660b63f7a737d11d4c96a-comps-Everything.x86_64.xml.gz: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')[0m
[32m* 11-02:23:11 (3777) [INFO] Trying other mirror.[0m
[32m* 11-02:23:41 (3777) [INFO] [0m
[32m* 11-02:23:41 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 11-02:23:41 (3787) [INFO] [0m
[33m* 11-02:23:41 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 11-02:23:41 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 11-02:23:41 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 11-02:23:41 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/z3JYbtNnxC/ea_profile.json[0m
[32m* 11-02:23:43 (1619) [INFO] Backed up EA4 profile to /tmp/z3JYbtNnxC/ea_profile.json[0m
[33m* 11-02:23:43 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 11-02:23:43 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 11-02:23:43 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 12-02:22:12 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 12-02:22:12 (3473) [ERROR] http://74.50.120.123/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://74.50.120.123/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/b929919c9eefac4a58217cc7370fbde7939e699ea5df136c70ee00c6f20f2934-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://centos.vargonen.com/centos/7.9.2009/updates/x86_64/repodata/de655a1791702b3522d4ab79d385a605d016c8d60b0f0e5e1149438dbf51726c-other.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
Trying other mirror.
http://centos.vargonen.com/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on http://centos.vargonen.com/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.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/c1a544dd5be55c80923d2ee8711caf908a843411c9450650175bc6e310dfdd53-other.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/c1a544dd5be55c80923d2ee8711caf908a843411c9450650175bc6e310dfdd53-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/dd18338d38d9c6b4c0bb1898fbd4f769c6758b90e8723c191926fd81a1dd624c-prestodelta.xml.gz: [Errno 12] Timeout on http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/dd18338d38d9c6b4c0bb1898fbd4f769c6758b90e8723c191926fd81a1dd624c-prestodelta.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://185.15.22.168/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 12] Timeout on http://185.15.22.168/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://mirror.verinomi.com/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://103.72.162.35/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
[0m
[33m* 12-02:22:12 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 12-02:22:13 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 12-02:22:13 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 12-02:22:13 (3767) [INFO] [0m
[32m* 12-02:22:13 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 12-02:22:13 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 12-02:22:13 (3777) [INFO]               : epel extras updates[0m
[32m* 12-02:22:14 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 12-02:22:14 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 12-02:22:14 (3787) [INFO] [0m
[32m* 12-02:22:14 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 12-02:22:14 (3767) [INFO] [0m
[32m* 12-02:22:14 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 12-02:22:15 (3777) [INFO] Determining fastest mirrors[0m
[32m* 12-02:22:38 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 12-02:22:38 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 12-02:22:38 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 12-02:22:38 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 12-02:22:38 (3777) [INFO]  * epel: mirror.ps.kz[0m
[32m* 12-02:22:38 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 12-02:22:38 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 12-02:23:15 (3777) [INFO] http://mirror.radoreservers.com/centos/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://mirror.radoreservers.com/centos/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')[0m
[32m* 12-02:23:15 (3777) [INFO] Trying other mirror.[0m
[32m* 12-02:23:46 (3777) [INFO] [0m
[32m* 12-02:23:46 (3777) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates[0m
[32m* 12-02:23:46 (3787) [INFO] [0m
[33m* 12-02:23:46 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 12-02:23:46 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 12-02:23:46 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 12-02:23:46 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0vOkGW3BcQ/ea_profile.json[0m
[32m* 12-02:23:48 (1619) [INFO] Backed up EA4 profile to /tmp/0vOkGW3BcQ/ea_profile.json[0m
[33m* 12-02:23:48 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 12-02:23:49 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 12-02:23:49 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 12-12:43:07 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 12-12:43:07 (3473) [ERROR] http://centos.vargonen.com/centos/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://centos.vargonen.com/centos/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://centos.vargonen.com/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/f04cb61dc5cb0a5712255776bf6b708d12b048ed90bc3b19222cb0ac59f45d12-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/b929919c9eefac4a58217cc7370fbde7939e699ea5df136c70ee00c6f20f2934-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/fb7e440eb00b353b845d2abac461e26b3dcd06f82b0632cd80cff2799ea5cea5-prestodelta.xml.gz: [Errno 12] Timeout on http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/fb7e440eb00b353b845d2abac461e26b3dcd06f82b0632cd80cff2799ea5cea5-prestodelta.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
[0m
[33m* 12-12:43:07 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 12-12:43:07 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 12-12:43:07 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 12-12:43:07 (3767) [INFO] [0m
[32m* 12-12:43:08 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 12-12:43:08 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 12-12:43:08 (3777) [INFO]               : epel extras updates[0m
[32m* 12-12:43:08 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 12-12:43:08 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 12-12:43:08 (3787) [INFO] [0m
[32m* 12-12:43:08 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 12-12:43:08 (3767) [INFO] [0m
[32m* 12-12:43:08 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 12-12:43:09 (3777) [INFO] Determining fastest mirrors[0m
[32m* 12-12:43:32 (3777) [INFO]  * EA4: 185.157.208.252[0m
[32m* 12-12:43:32 (3777) [INFO]  * cpanel-addons-production-feed: 185.157.208.252[0m
[32m* 12-12:43:32 (3777) [INFO]  * cpanel-plugins: 185.157.208.252[0m
[32m* 12-12:43:32 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 12-12:43:32 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 12-12:43:32 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 12-12:43:32 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 12-12:44:49 (3777) [INFO] http://istanbul.centos-mirror.guzel.net.tr/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://istanbul.centos-mirror.guzel.net.tr/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')[0m
[32m* 12-12:44:49 (3777) [INFO] Trying other mirror.[0m
[32m* 12-12:45:05 (3787) [INFO] [0m
[32m* 12-12:45:05 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 12-12:45:05 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 12-12:45:05 (3767) [INFO] [0m
[32m* 12-12:45:05 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 12-12:45:07 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 12-12:45:07 (3787) [INFO] [0m
[32m* 12-12:45:07 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 12-12:45:07 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ImIzsiCfTP/ea_profile.json[0m
[32m* 12-12:45:08 (1619) [INFO] Backed up EA4 profile to /tmp/ImIzsiCfTP/ea_profile.json[0m
[33m* 12-12:45:08 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 12-12:45:09 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 12-12:45:09 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 13-02:14:41 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 13-02:14:41 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 13-02:14:41 (3767) [INFO] [0m
[32m* 13-02:14:42 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 13-02:14:42 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 13-02:14:42 (3777) [INFO]               : epel extras updates[0m
[32m* 13-02:14:43 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 13-02:14:43 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 13-02:14:43 (3787) [INFO] [0m
[32m* 13-02:14:43 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 13-02:14:43 (3767) [INFO] [0m
[32m* 13-02:14:43 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 13-02:14:44 (3777) [INFO] Determining fastest mirrors[0m
[32m* 13-02:14:50 (3777) [INFO]  * EA4: 185.157.208.252[0m
[32m* 13-02:14:50 (3777) [INFO]  * cpanel-addons-production-feed: 185.157.208.252[0m
[32m* 13-02:14:50 (3777) [INFO]  * cpanel-plugins: 185.157.208.252[0m
[32m* 13-02:14:50 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 13-02:14:50 (3777) [INFO]  * epel: mirror.yer.az[0m
[32m* 13-02:14:50 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 13-02:14:50 (3777) [INFO]  * updates: mirror.netdirekt.com.tr[0m
[32m* 13-02:16:05 (3787) [INFO] [0m
[32m* 13-02:16:05 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 13-02:16:05 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 13-02:16:05 (3767) [INFO] [0m
[32m* 13-02:16:06 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 13-02:16:07 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 13-02:16:07 (3787) [INFO] [0m
[32m* 13-02:16:07 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 13-02:16:07 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QdF4ddjmX_/ea_profile.json[0m
[32m* 13-02:16:09 (1619) [INFO] Backed up EA4 profile to /tmp/QdF4ddjmX_/ea_profile.json[0m
[33m* 13-02:16: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 13-02:16:10 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 13-02:16:10 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 13-15:55:13 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 13-15:55:13 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 13-15:55:13 (3767) [INFO] [0m
[32m* 13-15:55:13 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 13-15:55:13 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 13-15:55:13 (3777) [INFO]               : epel extras updates[0m
[32m* 13-15:55:14 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 13-15:55:14 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 13-15:55:14 (3787) [INFO] [0m
[32m* 13-15:55:14 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 13-15:55:14 (3767) [INFO] [0m
[32m* 13-15:55:14 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 13-15:55:14 (3777) [INFO] Determining fastest mirrors[0m
[32m* 13-15:55:21 (3777) [INFO] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was[0m
[32m* 13-15:55:21 (3777) [INFO] 14: curl#52 - "Empty reply from server"[0m
[32m* 13-15:55:21 (3777) [INFO] [0m
[32m* 13-15:55:21 (3777) [INFO] [0m
[32m* 13-15:55:21 (3777) [INFO]  One of the configured repositories failed (Unknown),[0m
[32m* 13-15:55:21 (3777) [INFO]  and yum doesn't have enough cached data to continue. At this point the only[0m
[32m* 13-15:55:21 (3777) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:[0m
[32m* 13-15:55:21 (3777) [INFO] [0m
[32m* 13-15:55:21 (3777) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.[0m
[32m* 13-15:55:21 (3777) [INFO] [0m
[32m* 13-15:55:21 (3777) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working[0m
[32m* 13-15:55:21 (3777) [INFO]         upstream. This is most often useful if you are using a newer[0m
[32m* 13-15:55:21 (3777) [INFO]         distribution release than is supported by the repository (and the[0m
[32m* 13-15:55:21 (3777) [INFO]         packages for the previous distribution release still work).[0m
[32m* 13-15:55:21 (3777) [INFO] [0m
[32m* 13-15:55:21 (3777) [INFO]      3. Run the command with the repository temporarily disabled[0m
[32m* 13-15:55:21 (3777) [INFO]             yum --disablerepo=<repoid> ...[0m
[32m* 13-15:55:21 (3777) [INFO] [0m
[32m* 13-15:55:21 (3777) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum[0m
[32m* 13-15:55:21 (3777) [INFO]         will then just ignore the repository until you permanently enable it[0m
[32m* 13-15:55:21 (3777) [INFO]         again or use --enablerepo for temporary usage:[0m
[32m* 13-15:55:21 (3777) [INFO] [0m
[32m* 13-15:55:21 (3777) [INFO]             yum-config-manager --disable <repoid>[0m
[32m* 13-15:55:21 (3777) [INFO]         or[0m
[32m* 13-15:55:21 (3777) [INFO]             subscription-manager repos --disable=<repoid>[0m
[32m* 13-15:55:21 (3777) [INFO] [0m
[32m* 13-15:55:21 (3777) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.[0m
[32m* 13-15:55:21 (3777) [INFO]         Note that yum will try to contact the repo. when it runs most commands,[0m
[32m* 13-15:55:21 (3777) [INFO]         so will have to try and fail each time (and thus. yum will be be much[0m
[32m* 13-15:55:21 (3777) [INFO]         slower). If it is a very temporary problem though, this is often a nice[0m
[32m* 13-15:55:21 (3777) [INFO]         compromise:[0m
[32m* 13-15:55:21 (3777) [INFO] [0m
[32m* 13-15:55:21 (3777) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true[0m
[32m* 13-15:55:21 (3777) [INFO] [0m
[32m* 13-15:55:21 (3777) [INFO] Cannot find a valid baseurl for repo: EA4/7/x86_64[0m
[32m* 13-15:55:21 (3787) [INFO] [0m
[33m* 13-15:55:21 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 13-15:55:21 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 13-15:55:21 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 13-15:55:21 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/g0URKbzPd4/ea_profile.json[0m
[32m* 13-15:56:15 (1619) [INFO] Backed up EA4 profile to /tmp/g0URKbzPd4/ea_profile.json[0m
[33m* 13-15:56:15 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 13-15:56:16 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 13-15:56:16 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 14-02:28:49 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 14-02:28:49 (3473) [ERROR] http://102.22.80.80/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://102.22.80.80/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/b929919c9eefac4a58217cc7370fbde7939e699ea5df136c70ee00c6f20f2934-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
[0m
[33m* 14-02:28:49 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 14-02:28:49 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 14-02:28:49 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 14-02:28:49 (3767) [INFO] [0m
[32m* 14-02:28:50 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 14-02:28:50 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 14-02:28:50 (3777) [INFO]               : epel extras updates[0m
[32m* 14-02:28:50 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 14-02:28:50 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 14-02:28:50 (3787) [INFO] [0m
[32m* 14-02:28:50 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 14-02:28:50 (3767) [INFO] [0m
[32m* 14-02:28:50 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 14-02:28:51 (3777) [INFO] Determining fastest mirrors[0m
[32m* 14-02:28:56 (3777) [INFO]  * EA4: 185.157.208.252[0m
[32m* 14-02:28:56 (3777) [INFO]  * cpanel-addons-production-feed: 185.157.208.252[0m
[32m* 14-02:28:56 (3777) [INFO]  * cpanel-plugins: 185.157.208.252[0m
[32m* 14-02:28:56 (3777) [INFO]  * base: mirror.netdirekt.com.tr[0m
[32m* 14-02:28:56 (3777) [INFO]  * epel: mirror.yer.az[0m
[32m* 14-02:28:56 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 14-02:28:56 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 14-02:29:38 (3787) [INFO] [0m
[32m* 14-02:29:38 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 14-02:29:38 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 14-02:29:38 (3767) [INFO] [0m
[32m* 14-02:29:38 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 14-02:29:40 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 14-02:29:40 (3787) [INFO] [0m
[32m* 14-02:29:40 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 14-02:29:40 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/N2bSX8spUs/ea_profile.json[0m
[32m* 14-02:29:41 (1619) [INFO] Backed up EA4 profile to /tmp/N2bSX8spUs/ea_profile.json[0m
[33m* 14-02:29:41 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 14-02:29:42 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 14-02:29:42 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 15-02:23:34 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 15-02:23:34 (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 30001 milliseconds with 0 out of 0 bytes received')
http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/repomd.xml: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://63.247.64.58/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 12] Timeout on http://63.247.64.58/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://203.174.85.202/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 12] Timeout on http://203.174.85.202/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.92/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://185.15.22.168/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 12] Timeout on http://185.15.22.168/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.252.152.1/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 12] Timeout on http://103.252.152.1/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.74.123.61/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 12] Timeout on http://208.74.123.61/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 12] Timeout on http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://185.157.208.252/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 12] Timeout on http://185.157.208.252/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://103.48.119.120/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 12] Timeout on http://103.48.119.120/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
[0m
[33m* 15-02:23:34 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 15-02:23:36 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 15-02:23:36 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 15-02:23:36 (3767) [INFO] [0m
[32m* 15-02:23:36 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 15-02:23:36 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 15-02:23:36 (3777) [INFO]               : epel extras updates[0m
[32m* 15-02:23:37 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 15-02:23:37 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 15-02:23:37 (3787) [INFO] [0m
[32m* 15-02:23:37 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 15-02:23:37 (3767) [INFO] [0m
[32m* 15-02:23:37 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 15-02:23:38 (3777) [INFO] Determining fastest mirrors[0m
[32m* 15-02:23:45 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 15-02:23:45 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 15-02:23:45 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 15-02:23:45 (3777) [INFO]  * base: mirror.natro.com[0m
[32m* 15-02:23:45 (3777) [INFO]  * epel: mirror.yer.az[0m
[32m* 15-02:23:45 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 15-02:23:45 (3777) [INFO]  * updates: mirror.natro.com[0m
[32m* 15-02:24:10 (3787) [INFO] [0m
[32m* 15-02:24:10 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 15-02:24:10 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 15-02:24:10 (3767) [INFO] [0m
[32m* 15-02:24:11 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 15-02:24:17 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 15-02:24:17 (3787) [INFO] [0m
[32m* 15-02:24:17 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 15-02:24:17 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7b9U_Vcc7T/ea_profile.json[0m
[32m* 15-02:24:18 (1619) [INFO] Backed up EA4 profile to /tmp/7b9U_Vcc7T/ea_profile.json[0m
[33m* 15-02:24: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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 15-02:24:19 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 15-02:24:19 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[32m* 16-02:14:43 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 16-02:14:44 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 16-02:14:44 (3767) [INFO] [0m
[32m* 16-02:14:45 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 16-02:14:45 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 16-02:14:45 (3777) [INFO]               : epel extras updates[0m
[32m* 16-02:14:45 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 16-02:14:45 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 16-02:14:46 (3787) [INFO] [0m
[32m* 16-02:14:46 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 16-02:14:46 (3767) [INFO] [0m
[32m* 16-02:14:46 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 16-02:14:46 (3777) [INFO] Determining fastest mirrors[0m
[32m* 16-02:14:53 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 16-02:14:53 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 16-02:14:53 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 16-02:14:53 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 16-02:14:53 (3777) [INFO]  * epel: mirror.yer.az[0m
[32m* 16-02:14:53 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 16-02:14:53 (3777) [INFO]  * updates: mirror.netdirekt.com.tr[0m
[32m* 16-02:15:21 (3787) [INFO] [0m
[32m* 16-02:15:21 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 16-02:15:21 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 16-02:15:21 (3767) [INFO] [0m
[32m* 16-02:15:22 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 16-02:15:23 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 16-02:15:23 (3787) [INFO] [0m
[32m* 16-02:15:23 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 16-02:15:23 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8ZZZyryGar/ea_profile.json[0m
[32m* 16-02:15:24 (1619) [INFO] Backed up EA4 profile to /tmp/8ZZZyryGar/ea_profile.json[0m
[33m* 16-02:15:24 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 16-02:15:25 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 16-02:15:25 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 17-02:22:43 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 17-02:22:43 (3473) [ERROR] http://centos.vargonen.com/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
Trying other mirror.
http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://185.125.185.32/cpanelsync/repos/CentOS/7/EA4/repodata/02a5357c910582176625e46a086a6bf123f5e0c31d548dc3fe95c2c9f88a49ac-filelists.sqlite.bz2: [Errno 12] Timeout on http://185.125.185.32/cpanelsync/repos/CentOS/7/EA4/repodata/02a5357c910582176625e46a086a6bf123f5e0c31d548dc3fe95c2c9f88a49ac-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/02a5357c910582176625e46a086a6bf123f5e0c31d548dc3fe95c2c9f88a49ac-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://mirror.sabay.com.kh/epel/7/x86_64/repodata/2734f0809fae366693dc78eddee25d5746efd242550d56a828c6a78b262f91b2-filelists.sqlite.bz2: [Errno 12] Timeout on https://mirror.sabay.com.kh/epel/7/x86_64/repodata/2734f0809fae366693dc78eddee25d5746efd242550d56a828c6a78b262f91b2-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirror.verinomi.com/centos/7.9.2009/extras/x86_64/repodata/a9895ef0dcbbc894e0c3c35aee749164531a7eadac3a07380418201ed9cdb28c-filelists.sqlite.bz2: [Errno 12] Timeout on http://mirror.verinomi.com/centos/7.9.2009/extras/x86_64/repodata/a9895ef0dcbbc894e0c3c35aee749164531a7eadac3a07380418201ed9cdb28c-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.101.161.235/cpanelsync/repos/CentOS/7/EA4/repodata/02a5357c910582176625e46a086a6bf123f5e0c31d548dc3fe95c2c9f88a49ac-filelists.sqlite.bz2: [Errno 12] Timeout on http://103.101.161.235/cpanelsync/repos/CentOS/7/EA4/repodata/02a5357c910582176625e46a086a6bf123f5e0c31d548dc3fe95c2c9f88a49ac-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 12] Timeout on http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.72.162.35/cpanelsync/repos/CentOS/7/EA4/repodata/02a5357c910582176625e46a086a6bf123f5e0c31d548dc3fe95c2c9f88a49ac-filelists.sqlite.bz2: [Errno 12] Timeout on http://103.72.162.35/cpanelsync/repos/CentOS/7/EA4/repodata/02a5357c910582176625e46a086a6bf123f5e0c31d548dc3fe95c2c9f88a49ac-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.17.8.8/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 12] Timeout on http://103.17.8.8/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/02a5357c910582176625e46a086a6bf123f5e0c31d548dc3fe95c2c9f88a49ac-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://184.94.196.94/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://201.159.169.169/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 12] Timeout on http://201.159.169.169/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://27.50.85.8/cpanelsync/repos/CentOS/7/EA4/repodata/02a5357c910582176625e46a086a6bf123f5e0c31d548dc3fe95c2c9f88a49ac-filelists.sqlite.bz2: [Errno 12] Timeout on http://27.50.85.8/cpanelsync/repos/CentOS/7/EA4/repodata/02a5357c910582176625e46a086a6bf123f5e0c31d548dc3fe95c2c9f88a49ac-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://102.22.80.80/cpanelsync/repos/CentOS/7/EA4/repodata/02a5357c910582176625e46a086a6bf123f5e0c31d548dc3fe95c2c9f88a49ac-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://203.174.85.202/cpanelsync/repos/CentOS/7/EA4/repodata/02a5357c910582176625e46a086a6bf123f5e0c31d548dc3fe95c2c9f88a49ac-filelists.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://45.228.65.220/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 12] Timeout on http://45.228.65.220/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://102.22.80.80/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 12] Timeout on http://102.22.80.80/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://74.50.120.123/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 12] Timeout on http://74.50.120.123/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://185.125.185.32/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://138.118.173.126/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://184.94.196.92/cpanelsync/repos/CentOS/7/EA4/repodata/c27b10f4976f76c11aca1af6d02e387915ea7c85573bdc270119fac8ed5a6756-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
[0m
[33m* 17-02:22:43 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 17-02:22:44 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 17-02:22:44 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 17-02:22:44 (3767) [INFO] [0m
[32m* 17-02:22:44 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 17-02:22:44 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 17-02:22:44 (3777) [INFO]               : epel extras updates[0m
[32m* 17-02:22:45 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 17-02:22:45 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 17-02:22:45 (3787) [INFO] [0m
[32m* 17-02:22:45 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 17-02:22:45 (3767) [INFO] [0m
[32m* 17-02:22:45 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 17-02:22:45 (3777) [INFO] Determining fastest mirrors[0m
[32m* 17-02:22:55 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 17-02:22:55 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 17-02:22:55 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 17-02:22:55 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 17-02:22:55 (3777) [INFO]  * epel: repo.extreme-ix.org[0m
[32m* 17-02:22:55 (3777) [INFO]  * extras: mirror.natro.com[0m
[32m* 17-02:22:55 (3777) [INFO]  * updates: repo.boun.edu.tr[0m
[32m* 17-02:23:30 (3787) [INFO] [0m
[32m* 17-02:23:30 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 17-02:23:30 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 17-02:23:30 (3767) [INFO] [0m
[32m* 17-02:23:30 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 17-02:23:32 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 17-02:23:32 (3787) [INFO] [0m
[32m* 17-02:23:32 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 17-02:23:32 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tvDXLuZkE8/ea_profile.json[0m
[32m* 17-02:23:33 (1619) [INFO] Backed up EA4 profile to /tmp/tvDXLuZkE8/ea_profile.json[0m
[33m* 17-02:23:33 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 17-02:23:34 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 17-02:23:34 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 18-02:26:54 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 18-02:26:54 (3473) [ERROR] http://mirror.centos.jt.iq/7.9.2009/updates/x86_64/repodata/de655a1791702b3522d4ab79d385a605d016c8d60b0f0e5e1149438dbf51726c-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.centos.jt.iq/7.9.2009/updates/x86_64/repodata/de655a1791702b3522d4ab79d385a605d016c8d60b0f0e5e1149438dbf51726c-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://centos.turhost.com/7.9.2009/updates/x86_64/repodata/de655a1791702b3522d4ab79d385a605d016c8d60b0f0e5e1149438dbf51726c-other.sqlite.bz2: [Errno 12] Timeout on http://centos.turhost.com/7.9.2009/updates/x86_64/repodata/de655a1791702b3522d4ab79d385a605d016c8d60b0f0e5e1149438dbf51726c-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirror.saglayici.com/centos/7.9.2009/updates/x86_64/repodata/de655a1791702b3522d4ab79d385a605d016c8d60b0f0e5e1149438dbf51726c-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.saglayici.com/centos/7.9.2009/updates/x86_64/repodata/de655a1791702b3522d4ab79d385a605d016c8d60b0f0e5e1149438dbf51726c-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
[0m
[33m* 18-02:26:54 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 18-02:26:55 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 18-02:26:55 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 18-02:26:55 (3767) [INFO] [0m
[32m* 18-02:26:55 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 18-02:26:55 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 18-02:26:55 (3777) [INFO]               : epel extras updates[0m
[32m* 18-02:26:56 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 18-02:26:56 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 18-02:26:56 (3787) [INFO] [0m
[32m* 18-02:26:56 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 18-02:26:56 (3767) [INFO] [0m
[32m* 18-02:26:56 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 18-02:26:56 (3777) [INFO] Determining fastest mirrors[0m
[32m* 18-02:27:01 (3777) [INFO]  * EA4: 178.18.193.52[0m
[32m* 18-02:27:01 (3777) [INFO]  * cpanel-addons-production-feed: 178.18.193.52[0m
[32m* 18-02:27:01 (3777) [INFO]  * cpanel-plugins: 178.18.193.52[0m
[32m* 18-02:27:01 (3777) [INFO]  * base: ftp.linux.org.tr[0m
[32m* 18-02:27:01 (3777) [INFO]  * epel: mirror.yer.az[0m
[32m* 18-02:27:01 (3777) [INFO]  * extras: mirror.netdirekt.com.tr[0m
[32m* 18-02:27:01 (3777) [INFO]  * updates: ftp.linux.org.tr[0m
[32m* 18-02:28:10 (3787) [INFO] [0m
[32m* 18-02:28:10 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 18-02:28:10 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 18-02:28:10 (3767) [INFO] [0m
[32m* 18-02:28:11 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 18-02:28:12 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 18-02:28:12 (3787) [INFO] [0m
[32m* 18-02:28:12 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 18-02:28:12 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2fSCyF4vQv/ea_profile.json[0m
[32m* 18-02:28:13 (1619) [INFO] Backed up EA4 profile to /tmp/2fSCyF4vQv/ea_profile.json[0m
[33m* 18-02:28:13 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 18-02:28:14 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 18-02:28:14 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 19-02:22:35 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 19-02:22:37 (3473) [ERROR] http://centos.vargonen.com/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
Trying other mirror.
[0m
[33m* 19-02:22:37 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 19-02:22:37 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 19-02:22:37 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 19-02:22:37 (3767) [INFO] [0m
[32m* 19-02:22:37 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 19-02:22:37 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base[0m
[32m* 19-02:22:37 (3777) [INFO]               : epel extras updates[0m
[32m* 19-02:22:38 (3777) [INFO] Cleaning up list of fastest mirrors[0m
[32m* 19-02:22:38 (3777) [INFO] Other repos take up 396 k of disk space (use --verbose for details)[0m
[32m* 19-02:22:38 (3787) [INFO] [0m
[32m* 19-02:22:38 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 19-02:22:38 (3767) [INFO] [0m
[32m* 19-02:22:38 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks[0m
[32m* 19-02:22:39 (3777) [INFO] Determining fastest mirrors[0m
[32m* 19-02:22:43 (3777) [INFO]  * EA4: 185.15.22.168[0m
[32m* 19-02:22:43 (3777) [INFO]  * cpanel-addons-production-feed: 185.15.22.168[0m
[32m* 19-02:22:43 (3777) [INFO]  * cpanel-plugins: 185.15.22.168[0m
[32m* 19-02:22:43 (3777) [INFO]  * base: repo.boun.edu.tr[0m
[32m* 19-02:22:43 (3777) [INFO]  * epel: mirror.yer.az[0m
[32m* 19-02:22:43 (3777) [INFO]  * extras: repo.boun.edu.tr[0m
[32m* 19-02:22:43 (3777) [INFO]  * updates: mirror.alastyr.com[0m
[32m* 19-02:23:29 (3787) [INFO] [0m
[32m* 19-02:23:29 (3328) [INFO] Checking /scripts/sysup[0m
[32m* 19-02:23:29 (3766) [INFO] Running: /scripts/sysup[0m
[32m* 19-02:23:29 (3767) [INFO] [0m
[32m* 19-02:23:30 (3777) [INFO] checkyum version 22.3  (excludes: bind-chroot)[0m
[32m* 19-02:23:31 (3777) [INFO]   All Needed Packages are already installed.[0m
[32m* 19-02:23:31 (3787) [INFO] [0m
[32m* 19-02:23:31 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 19-02:23:31 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Z5p5nS4wMc/ea_profile.json[0m
[32m* 19-02:23:33 (1619) [INFO] Backed up EA4 profile to /tmp/Z5p5nS4wMc/ea_profile.json[0m
[33m* 19-02:23:33 (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-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

[0m
[33m* 19-02:23:33 (2667) [WARN] *** Elevation Blocker detected: ***
This script (version 1) 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.

[0m
[33m* 19-02:23:33 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
[35m* 20-02:25:03 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading[0m
[35m* 20-02:25:03 (3473) [ERROR] error: rpmdb: BDB0113 Thread/process 29205/140453585127232 failed: BDB1507 Thread died in Berkeley DB library
error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db5 -  (-30973)
error: cannot open Packages database in /var/lib/rpm
CRITICAL:yum.main:

Error: rpmdb open failed
[0m
[33m* 20-02:25:03 (2667) [WARN] *** Elevation Blocker detected: ***
yum is not stable
[0m
[32m* 20-02:25:03 (3321) [INFO] Checking if your system is up to date: [0m
[32m* 20-02:25:03 (3766) [INFO] Running: /usr/bin/yum clean all[0m
[32m* 20-02:25:03 (3767) [INFO] [0m
[32m* 20-02:25:05 (3777) [INFO] error: rpmdb: BDB0113 Thread/process 29205/140453585127232 failed: BDB1507 Thread died in Berkeley DB library[0m
[32m* 20-02:25:05 (3777) [INFO] error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery[0m
[32m* 20-02:25:05 (3777) [INFO] error: cannot open Packages index using db5 -  (-30973)[0m
[32m* 20-02:25:05 (3777) [INFO] error: cannot open Packages database in /var/lib/rpm[0m
[32m* 20-02:25:05 (3777) [INFO] CRITICAL:yum.main:[0m
[32m* 20-02:25:05 (3777) [INFO] [0m
[32m* 20-02:25:05 (3777) [INFO] Error: rpmdb open failed[0m
[32m* 20-02:25:05 (3787) [INFO] [0m
[32m* 20-02:25:05 (3766) [INFO] Running: /usr/bin/yum check-update[0m
[32m* 20-02:25:05 (3767) [INFO] [0m
[32m* 20-02:25:37 (3777) [INFO] error: rpmdb: BDB0113 Thread/process 29205/140453585127232 failed: BDB1507 Thread died in Berkeley DB library[0m
[32m* 20-02:25:37 (3777) [INFO] error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery[0m
[32m* 20-02:25:37 (3777) [INFO] error: cannot open Packages index using db5 -  (-30973)[0m
[32m* 20-02:25:37 (3777) [INFO] error: cannot open Packages database in /var/lib/rpm[0m
[32m* 20-02:25:37 (3777) [INFO] CRITICAL:yum.main:[0m
[32m* 20-02:25:37 (3777) [INFO] [0m
[32m* 20-02:25:37 (3777) [INFO] Error: rpmdb open failed[0m
[32m* 20-02:25:37 (3787) [INFO] [0m
[33m* 20-02:25:37 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update[0m
[33m* 20-02:25:37 (2667) [WARN] *** Elevation Blocker detected: ***
System is not up to date
[0m
[32m* 20-02:25:37 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.[0m
[32m* 20-02:25:37 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nxNUEzESlB/ea_profile.json[0m
[33m* 20-02:26:44 (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/nxNUEzESlB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 1596.
[0m
[33m* 20-02:26:45 (688) [WARN] Please fix the detected issues before performing the elevation process.
[0m
* 2023-01-20 16:12:12 (3552) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-01-20 16:12:12 (3553) [[31mERROR[0m] http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.74.123.61/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://185.157.208.252/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: [Errno 12] Timeout on http://185.157.208.252/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://74.50.120.123/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: [Errno 12] Timeout on http://74.50.120.123/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: [Errno 12] Timeout on http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: [Errno 12] Timeout on http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://102.22.80.80/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: [Errno 12] Timeout on http://102.22.80.80/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.120.66.133/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-01-20 16:12:12 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-01-20 16:12:13 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-01-20 16:12:13 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-01-20 16:12:13 (3898) [[32mINFO[0m] 
* 2023-01-20 16:12:13 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-20 16:12:13 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-01-20 16:12:13 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-01-20 16:12:13 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-01-20 16:12:13 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-01-20 16:12:13 (3929) [[32mINFO[0m] 
* 2023-01-20 16:12:13 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-01-20 16:12:13 (3898) [[32mINFO[0m] 
* 2023-01-20 16:13:05 (3912) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/5db6f8ed3235709d55eacd6f5e8df08beee6c74f691660b63f7a737d11d4c96a-comps-Everything.x86_64.xml.gz: [Errno 12] Timeout on http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/5db6f8ed3235709d55eacd6f5e8df08beee6c74f691660b63f7a737d11d4c96a-comps-Everything.x86_64.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-01-20 16:13:05 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-01-20 16:13:23 (3929) [[32mINFO[0m] 
* 2023-01-20 16:13:23 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-01-20 16:13:23 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-01-20 16:13:23 (3898) [[32mINFO[0m] 
* 2023-01-20 16:13:24 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-01-20 16:13:25 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-01-20 16:13:25 (3929) [[32mINFO[0m] 
* 2023-01-20 16:13:25 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-20 16:13:25 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1LHq1SkWwA/ea_profile.json
* 2023-01-20 16:13:26 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/1LHq1SkWwA/ea_profile.json
* 2023-01-20 16:13:26 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-01-20 16:13:28 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-01-21 02:17:30 (3552) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-01-21 02:17:30 (3553) [[31mERROR[0m] http://208.74.123.61/cpanelsync/repos/CentOS/7/EA4/repodata/bcb44e5adb7b0b340212a181b358779cb4b6a1d6c77541d27eed2a0c9ed3c08c-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://centos.vargonen.com/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/90b539d32756acc9401192d4bb2926e3ae62f664cfc37787eb1e8a8210422de5-filelists.sqlite.bz2: [Errno 12] Timeout on https://repo.extreme-ix.org/epel/7/x86_64/repodata/90b539d32756acc9401192d4bb2926e3ae62f664cfc37787eb1e8a8210422de5-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
* 2023-01-21 02:17:30 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-01-21 02:17:30 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-01-21 02:17:30 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-01-21 02:17:30 (3898) [[32mINFO[0m] 
* 2023-01-21 02:17:30 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-21 02:17:30 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-01-21 02:17:30 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-01-21 02:17:31 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-01-21 02:17:31 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-01-21 02:17:31 (3929) [[32mINFO[0m] 
* 2023-01-21 02:17:31 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-01-21 02:17:31 (3898) [[32mINFO[0m] 
* 2023-01-21 02:17:42 (3912) [[32mINFO[0m] http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/repomd.xml: [Errno 14] curl#52 - "Empty reply from server"
* 2023-01-21 02:17:42 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-01-21 02:17:53 (3912) [[32mINFO[0m] http://centos.vargonen.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
* 2023-01-21 02:17:53 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-01-21 02:18:41 (3929) [[32mINFO[0m] 
* 2023-01-21 02:18:41 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-01-21 02:18:41 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-01-21 02:18:41 (3898) [[32mINFO[0m] 
* 2023-01-21 02:18:41 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-01-21 02:18:43 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-01-21 02:18:44 (3929) [[32mINFO[0m] 
* 2023-01-21 02:18:44 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-21 02:18:44 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hdyFCLv9bS/ea_profile.json
* 2023-01-21 02:18:45 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/hdyFCLv9bS/ea_profile.json
* 2023-01-21 02:18:45 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-01-21 02:18:46 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-01-22 02:22:20 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-01-22 02:22:20 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-01-22 02:22:20 (3898) [[32mINFO[0m] 
* 2023-01-22 02:22:20 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-22 02:22:20 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-01-22 02:22:20 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-01-22 02:22:22 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-01-22 02:22:22 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-01-22 02:22:22 (3929) [[32mINFO[0m] 
* 2023-01-22 02:22:22 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-01-22 02:22:22 (3898) [[32mINFO[0m] 
* 2023-01-22 02:23:04 (3929) [[32mINFO[0m] 
* 2023-01-22 02:23:04 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-01-22 02:23:04 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-01-22 02:23:04 (3898) [[32mINFO[0m] 
* 2023-01-22 02:23:04 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-01-22 02:23:06 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-01-22 02:23:06 (3929) [[32mINFO[0m] 
* 2023-01-22 02:23:06 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-22 02:23:06 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/eZabZS7mmb/ea_profile.json
* 2023-01-22 02:23:08 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/eZabZS7mmb/ea_profile.json
* 2023-01-22 02:23:08 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-01-22 02:23:09 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-01-23 02:17:38 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-01-23 02:17:40 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-01-23 02:17:40 (3898) [[32mINFO[0m] 
* 2023-01-23 02:17:40 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-23 02:17:40 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-01-23 02:17:41 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-01-23 02:17:41 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-01-23 02:17:41 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-01-23 02:17:41 (3929) [[32mINFO[0m] 
* 2023-01-23 02:17:41 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-01-23 02:17:41 (3898) [[32mINFO[0m] 
* 2023-01-23 02:18:18 (3929) [[32mINFO[0m] 
* 2023-01-23 02:18:18 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-01-23 02:18:18 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-01-23 02:18:18 (3898) [[32mINFO[0m] 
* 2023-01-23 02:18:19 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-01-23 02:18:20 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-01-23 02:18:20 (3929) [[32mINFO[0m] 
* 2023-01-23 02:18:20 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-23 02:18:20 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1GIPZyjX5j/ea_profile.json
* 2023-01-23 02:18:21 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/1GIPZyjX5j/ea_profile.json
* 2023-01-23 02:18:21 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-01-23 02:18:23 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-01-24 02:14:05 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-01-24 02:14:05 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-01-24 02:14:05 (3898) [[32mINFO[0m] 
* 2023-01-24 02:14:05 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-24 02:14:05 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-01-24 02:14:05 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-01-24 02:14:06 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-01-24 02:14:06 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-01-24 02:14:06 (3929) [[32mINFO[0m] 
* 2023-01-24 02:14:06 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-01-24 02:14:06 (3898) [[32mINFO[0m] 
* 2023-01-24 02:15:01 (3929) [[32mINFO[0m] 
* 2023-01-24 02:15:01 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-01-24 02:15:01 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-01-24 02:15:01 (3898) [[32mINFO[0m] 
* 2023-01-24 02:15:01 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-01-24 02:15:03 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-01-24 02:15:03 (3929) [[32mINFO[0m] 
* 2023-01-24 02:15:03 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-24 02:15:03 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/I0pY2E0yGj/ea_profile.json
* 2023-01-24 02:15:04 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/I0pY2E0yGj/ea_profile.json
* 2023-01-24 02:15:04 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-01-24 02:15:06 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-01-25 02:15:41 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-01-25 02:15:41 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-01-25 02:15:41 (3898) [[32mINFO[0m] 
* 2023-01-25 02:15:44 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-25 02:15:45 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-01-25 02:15:45 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-01-25 02:15:47 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-01-25 02:15:47 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-01-25 02:15:47 (3929) [[32mINFO[0m] 
* 2023-01-25 02:15:47 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-01-25 02:15:47 (3898) [[32mINFO[0m] 
* 2023-01-25 02:16:27 (3929) [[32mINFO[0m] 
* 2023-01-25 02:16:27 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-01-25 02:16:27 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-01-25 02:16:27 (3898) [[32mINFO[0m] 
* 2023-01-25 02:16:28 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-01-25 02:16:47 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-01-25 02:16:47 (3929) [[32mINFO[0m] 
* 2023-01-25 02:16:47 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-25 02:16:47 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/E22nwtY971/ea_profile.json
* 2023-01-25 02:16:51 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/E22nwtY971/ea_profile.json
* 2023-01-25 02:16:51 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-01-25 02:16:53 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-01-26 02:14:48 (3552) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-01-26 02:14:48 (3553) [[31mERROR[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/dc0cf97163bf50692e9f974baa75e63af29d5d6769ab7dafa2693eb9010fd318-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://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/0b040891a6169c1d1cf2de1fd8e5d0acb702cb8d591c18ba08c0c797cc18a5bd-other.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/0b040891a6169c1d1cf2de1fd8e5d0acb702cb8d591c18ba08c0c797cc18a5bd-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.120.66.133/cpanelsync/repos/CentOS/7/EA4/repodata/0b040891a6169c1d1cf2de1fd8e5d0acb702cb8d591c18ba08c0c797cc18a5bd-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-01-26 02:14:48 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-01-26 02:14:49 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-01-26 02:14:49 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-01-26 02:14:49 (3898) [[32mINFO[0m] 
* 2023-01-26 02:14:49 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-26 02:14:49 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-01-26 02:14:49 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-01-26 02:14:49 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-01-26 02:14:49 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-01-26 02:14:49 (3929) [[32mINFO[0m] 
* 2023-01-26 02:14:49 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-01-26 02:14:49 (3898) [[32mINFO[0m] 
* 2023-01-26 02:15:02 (3912) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/b277efe6b7cd93a142299b0ce95a34c464e0422c5da0c05b53e8f705f1eb8365-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-01-26 02:15:02 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-01-26 02:15:02 (3912) [[32mINFO[0m] To address this issue please refer to the below wiki article 
* 2023-01-26 02:15:02 (3912) [[32mINFO[0m] 
* 2023-01-26 02:15:02 (3912) [[32mINFO[0m] https://wiki.centos.org/yum-errors
* 2023-01-26 02:15:02 (3912) [[32mINFO[0m] 
* 2023-01-26 02:15:02 (3912) [[32mINFO[0m] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2023-01-26 02:15:02 (3912) [[32mINFO[0m] 
* 2023-01-26 02:15:35 (3929) [[32mINFO[0m] 
* 2023-01-26 02:15:35 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-01-26 02:15:35 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-01-26 02:15:35 (3898) [[32mINFO[0m] 
* 2023-01-26 02:15:35 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-01-26 02:15:37 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-01-26 02:15:37 (3929) [[32mINFO[0m] 
* 2023-01-26 02:15:37 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-26 02:15:37 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uSaPMux7wO/ea_profile.json
* 2023-01-26 02:15:39 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/uSaPMux7wO/ea_profile.json
* 2023-01-26 02:15:39 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-01-26 02:15:40 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-01-27 02:14:55 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-01-27 02:14:55 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-01-27 02:14:55 (3898) [[32mINFO[0m] 
* 2023-01-27 02:14:55 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-27 02:14:55 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-01-27 02:14:55 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-01-27 02:14:55 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-01-27 02:14:55 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-01-27 02:14:55 (3929) [[32mINFO[0m] 
* 2023-01-27 02:14:55 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-01-27 02:14:55 (3898) [[32mINFO[0m] 
* 2023-01-27 02:15:30 (3929) [[32mINFO[0m] 
* 2023-01-27 02:15:30 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-01-27 02:15:30 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-01-27 02:15:30 (3898) [[32mINFO[0m] 
* 2023-01-27 02:15:31 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-01-27 02:15:32 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-01-27 02:15:32 (3929) [[32mINFO[0m] 
* 2023-01-27 02:15:32 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-27 02:15:32 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/F0fDwBNZbn/ea_profile.json
* 2023-01-27 02:15:33 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/F0fDwBNZbn/ea_profile.json
* 2023-01-27 02:15:33 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-01-27 02:15:34 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-01-27 15:50:52 (3552) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-01-27 15:50:52 (3553) [[31mERROR[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/772488c0b2ba6ee70267c0abacf09d065b0e3aa1b804ffca7a8873c95cd2bdcf-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://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/aa43d404c6e39a6d02b1746a4a224d6e118859c82c365c2141a4920dc7f4fe6c-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/d953c19917b805b05ce7fd623161f1c3bc126919c05aae315072c40386ff485a-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirrors.nipa.cloud/epel/7/x86_64/repodata/037259aec9f7dc3053d7f8254f5de0da767e51f2b22e8b733248734c1f380354-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/772488c0b2ba6ee70267c0abacf09d065b0e3aa1b804ffca7a8873c95cd2bdcf-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirrors.nipa.cloud/epel/7/x86_64/repodata/aa43d404c6e39a6d02b1746a4a224d6e118859c82c365c2141a4920dc7f4fe6c-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/d953c19917b805b05ce7fd623161f1c3bc126919c05aae315072c40386ff485a-prestodelta.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/037259aec9f7dc3053d7f8254f5de0da767e51f2b22e8b733248734c1f380354-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirrors.nipa.cloud/epel/7/x86_64/repodata/772488c0b2ba6ee70267c0abacf09d065b0e3aa1b804ffca7a8873c95cd2bdcf-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/037259aec9f7dc3053d7f8254f5de0da767e51f2b22e8b733248734c1f380354-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirror.yer.az/fedora-epel/7/x86_64/repodata/772488c0b2ba6ee70267c0abacf09d065b0e3aa1b804ffca7a8873c95cd2bdcf-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror.sabay.com.kh/epel/7/x86_64/repodata/aa43d404c6e39a6d02b1746a4a224d6e118859c82c365c2141a4920dc7f4fe6c-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror.yer.az/fedora-epel/7/x86_64/repodata/aa43d404c6e39a6d02b1746a4a224d6e118859c82c365c2141a4920dc7f4fe6c-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.dimensi.cloud/epel/7/x86_64/repodata/037259aec9f7dc3053d7f8254f5de0da767e51f2b22e8b733248734c1f380354-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.dimensi.cloud/epel/7/x86_64/repodata/037259aec9f7dc3053d7f8254f5de0da767e51f2b22e8b733248734c1f380354-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror.yer.az/fedora-epel/7/x86_64/repodata/037259aec9f7dc3053d7f8254f5de0da767e51f2b22e8b733248734c1f380354-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
* 2023-01-27 15:50:52 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-01-27 15:50:55 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-01-27 15:50:55 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-01-27 15:50:55 (3898) [[32mINFO[0m] 
* 2023-01-27 15:50:56 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-27 15:50:56 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-01-27 15:50:56 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-01-27 15:50:56 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-01-27 15:50:56 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-01-27 15:50:56 (3929) [[32mINFO[0m] 
* 2023-01-27 15:50:56 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-01-27 15:50:56 (3898) [[32mINFO[0m] 
* 2023-01-27 15:52:16 (3912) [[32mINFO[0m] http://208.74.123.61/cpanelsync/repos/CentOS/7/EA4/repodata/b00aa0b57c2bfa89eb0d64192caa50ab66b9afe65c32e2e605ec48b1eb5c0471-primary.sqlite.bz2: [Errno 12] Timeout on http://208.74.123.61/cpanelsync/repos/CentOS/7/EA4/repodata/b00aa0b57c2bfa89eb0d64192caa50ab66b9afe65c32e2e605ec48b1eb5c0471-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-01-27 15:52:16 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-01-27 15:52:23 (3912) [[32mINFO[0m] http://103.120.66.133/cpanelsync/repos/CentOS/7/EA4/repodata/b00aa0b57c2bfa89eb0d64192caa50ab66b9afe65c32e2e605ec48b1eb5c0471-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-01-27 15:52:23 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-01-27 15:52:46 (3929) [[32mINFO[0m] 
* 2023-01-27 15:52:46 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-01-27 15:52:46 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-01-27 15:52:46 (3898) [[32mINFO[0m] 
* 2023-01-27 15:52:46 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-01-27 15:52:50 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-01-27 15:52:50 (3929) [[32mINFO[0m] 
* 2023-01-27 15:52:50 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-27 15:52:50 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uqF9VhyGDT/ea_profile.json
* 2023-01-27 15:52:53 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/uqF9VhyGDT/ea_profile.json
* 2023-01-27 15:52:53 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-01-27 15:52:59 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-01-28 02:18:22 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-01-28 02:18:23 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-01-28 02:18:23 (3898) [[32mINFO[0m] 
* 2023-01-28 02:18:23 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-28 02:18:23 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-01-28 02:18:23 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-01-28 02:18:23 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-01-28 02:18:23 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-01-28 02:18:23 (3929) [[32mINFO[0m] 
* 2023-01-28 02:18:23 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-01-28 02:18:23 (3898) [[32mINFO[0m] 
* 2023-01-28 02:19:04 (3912) [[32mINFO[0m] 
* 2023-01-28 02:19:04 (3912) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-01-28 02:19:04 (3929) [[32mINFO[0m] 
* 2023-01-28 02:19:04 (3393) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-28 02:19:04 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-28 02:19:04 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-28 02:19:04 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rfWdBHefNo/ea_profile.json
* 2023-01-28 02:19:05 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/rfWdBHefNo/ea_profile.json
* 2023-01-28 02:19:05 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-01-28 02:19:07 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-01-29 02:14:14 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-01-29 02:14:15 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-01-29 02:14:15 (3898) [[32mINFO[0m] 
* 2023-01-29 02:14:15 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-29 02:14:16 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-01-29 02:14:16 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-01-29 02:14:16 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-01-29 02:14:16 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-01-29 02:14:16 (3929) [[32mINFO[0m] 
* 2023-01-29 02:14:16 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-01-29 02:14:16 (3898) [[32mINFO[0m] 
* 2023-01-29 02:14:56 (3912) [[32mINFO[0m] 
* 2023-01-29 02:14:56 (3912) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-01-29 02:14:56 (3929) [[32mINFO[0m] 
* 2023-01-29 02:14:56 (3393) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-29 02:14:56 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-29 02:14:56 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-29 02:14:56 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XZ1HgZYFGX/ea_profile.json
* 2023-01-29 02:14:58 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/XZ1HgZYFGX/ea_profile.json
* 2023-01-29 02:14:58 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-01-29 02:14:59 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-01-30 02:20:32 (3552) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-01-30 02:20:32 (3553) [[31mERROR[0m] http://185.157.208.252/cpanelsync/repos/CentOS/7/EA4/repodata/0b040891a6169c1d1cf2de1fd8e5d0acb702cb8d591c18ba08c0c797cc18a5bd-other.sqlite.bz2: [Errno 12] Timeout on http://185.157.208.252/cpanelsync/repos/CentOS/7/EA4/repodata/0b040891a6169c1d1cf2de1fd8e5d0acb702cb8d591c18ba08c0c797cc18a5bd-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/0b040891a6169c1d1cf2de1fd8e5d0acb702cb8d591c18ba08c0c797cc18a5bd-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-01-30 02:20:32 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-01-30 02:20:34 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-01-30 02:20:34 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-01-30 02:20:34 (3898) [[32mINFO[0m] 
* 2023-01-30 02:20:34 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-30 02:20:34 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-01-30 02:20:34 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-01-30 02:20:34 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-01-30 02:20:34 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-01-30 02:20:34 (3929) [[32mINFO[0m] 
* 2023-01-30 02:20:34 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-01-30 02:20:34 (3898) [[32mINFO[0m] 
* 2023-01-30 02:21:20 (3929) [[32mINFO[0m] 
* 2023-01-30 02:21:20 (3393) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-30 02:21:20 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-01-30 02:21:20 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-01-30 02:21:20 (3898) [[32mINFO[0m] 
* 2023-01-30 02:21:21 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-01-30 02:21:37 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot kernel)
* 2023-01-30 02:21:38 (3912) [[32mINFO[0m] error: rpmdb: BDB0113 Thread/process 13583/140120146569024 failed: BDB1507 Thread died in Berkeley DB library
* 2023-01-30 02:21:38 (3912) [[32mINFO[0m] error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
* 2023-01-30 02:21:38 (3912) [[32mINFO[0m] error: cannot open Packages index using db5 -  (-30973)
* 2023-01-30 02:21:38 (3912) [[32mINFO[0m] error: cannot open Packages database in /var/lib/rpm
* 2023-01-30 02:21:38 (3912) [[32mINFO[0m] CRITICAL:yum.main:
* 2023-01-30 02:21:38 (3912) [[32mINFO[0m] 
* 2023-01-30 02:21:38 (3912) [[32mINFO[0m] Error: rpmdb open failed
* 2023-01-30 02:21:38 (3912) [[32mINFO[0m] (XID pck25r) “/usr/bin/yum” reported error code “1” when it ended: 
* 2023-01-30 02:21:54 (3912) [[32mINFO[0m] E Sysup: Needed system packages were not installed: ImageMagick, aspell, at, autoconf, automake, bind, bind-devel, bind-libs, bind-utils, binutils, bison, boost-program-options, boost-serialization, bzip2, cairo, compat-db, coreutils, cpio, cpp, crontabs, curl, dpkg, e2fsprogs, e2fsprogs-devel, ea-cpanel-tools, ea-profiles-cpanel, expat, expat-devel, file, flex, fontconfig, freetype, ftp, gawk, gcc, gcc-c++, gd, gd-devel, gd-progs, gdbm, gdbm-devel, gettext, gettext-devel, ghostscript, giflib, glib2, glibc-devel, glibc-static, gmp, gnupg2, grubby, gzip, hunspell, hunspell-en, initscripts, iptables, json-c, kernel-headers, krb5-devel, less, libX11-devel, libXpm, libXpm-devel, libaio, libaio-devel, libdb, libevent, libgcc, libgomp, libicu, libidn, libidn-devel, libjpeg-turbo, libjpeg-turbo-devel, libmount, libpcap, libpng, libpng-devel, libstdc++, libstdc++-devel, libtiff, libtiff-devel, libtool, libtool-ltdl, libtool-ltdl-devel, libwmf, libxml2, libxml2-devel, libxslt, libxslt-devel, libzip, lsof, make, nano, ncurses, ncurses-devel, ncurses-term, net-tools, nscd, openssh, openssh-clients, openssh-server, openssl, openssl-devel, pam, pam-devel, pango, passwd, patch, pcre, pcre2, perl-CPAN, perl-Expect, perl-ExtUtils-MakeMaker, perl-IO-Tty, perl-JSON-XS, perl-Module-Build, perl-Try-Tiny, perl-YAML-Syck, perl-core, perl-devel, perl-libwww-perl, perl-local-lib, pixman, popt, procps-ng, psmisc, python, python-devel, python-docs, python-setuptools, python-tools, quota, quota-devel, rdate, rsync, sed, shadow-utils, smartmontools, strace, sysstat, tar, tcp_wrappers-devel, traceroute, unzip, urw-fonts, wget, which, xz, yum-plugin-universal-hooks, yum-utils, zip, zlib, zlib-devel
* 2023-01-30 02:21:54 (3929) [[32mINFO[0m] 
* 2023-01-30 02:21:54 (3410) [[33mWARN[0m] /scripts/sysup failed, please fix it and rerun it before upgrading.
* 2023-01-30 02:21:54 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-30 02:21:54 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-30 02:21:54 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EQqXk9_lH7/ea_profile.json
* 2023-01-30 02:21:56 (2694) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EQqXk9_lH7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 1644.
* 2023-01-30 02:21:56 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-01-30 02:21:58 (3552) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-01-30 02:21:58 (3553) [[31mERROR[0m] error: rpmdb: BDB0113 Thread/process 13583/140120146569024 failed: BDB1507 Thread died in Berkeley DB library
error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db5 -  (-30973)
error: cannot open Packages database in /var/lib/rpm
CRITICAL:yum.main:

Error: rpmdb open failed
* 2023-01-30 02:21:58 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-01-30 02:21:58 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-01-30 02:21:58 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-01-30 02:21:58 (3898) [[32mINFO[0m] 
* 2023-01-30 02:21:58 (3912) [[32mINFO[0m] error: rpmdb: BDB0113 Thread/process 13583/140120146569024 failed: BDB1507 Thread died in Berkeley DB library
* 2023-01-30 02:21:58 (3912) [[32mINFO[0m] error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
* 2023-01-30 02:21:58 (3912) [[32mINFO[0m] error: cannot open Packages index using db5 -  (-30973)
* 2023-01-30 02:21:58 (3912) [[32mINFO[0m] error: cannot open Packages database in /var/lib/rpm
* 2023-01-30 02:21:58 (3912) [[32mINFO[0m] CRITICAL:yum.main:
* 2023-01-30 02:21:58 (3912) [[32mINFO[0m] 
* 2023-01-30 02:21:58 (3912) [[32mINFO[0m] Error: rpmdb open failed
* 2023-01-30 02:21:58 (3929) [[32mINFO[0m] 
* 2023-01-30 02:21:58 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-01-30 02:21:58 (3898) [[32mINFO[0m] 
* 2023-01-30 02:21:59 (3912) [[32mINFO[0m] error: rpmdb: BDB0113 Thread/process 13583/140120146569024 failed: BDB1507 Thread died in Berkeley DB library
* 2023-01-30 02:21:59 (3912) [[32mINFO[0m] error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
* 2023-01-30 02:21:59 (3912) [[32mINFO[0m] error: cannot open Packages index using db5 -  (-30973)
* 2023-01-30 02:21:59 (3912) [[32mINFO[0m] error: cannot open Packages database in /var/lib/rpm
* 2023-01-30 02:21:59 (3912) [[32mINFO[0m] CRITICAL:yum.main:
* 2023-01-30 02:21:59 (3912) [[32mINFO[0m] 
* 2023-01-30 02:21:59 (3912) [[32mINFO[0m] Error: rpmdb open failed
* 2023-01-30 02:21:59 (3929) [[32mINFO[0m] 
* 2023-01-30 02:21:59 (3393) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-30 02:21:59 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-01-30 02:21:59 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-01-30 02:21:59 (3898) [[32mINFO[0m] 
* 2023-01-30 02:21:59 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-01-30 02:22:15 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot kernel)
* 2023-01-30 02:22:18 (3912) [[32mINFO[0m] error: rpmdb: BDB0113 Thread/process 13583/140120146569024 failed: BDB1507 Thread died in Berkeley DB library
* 2023-01-30 02:22:18 (3912) [[32mINFO[0m] error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
* 2023-01-30 02:22:18 (3912) [[32mINFO[0m] error: cannot open Packages index using db5 -  (-30973)
* 2023-01-30 02:22:18 (3912) [[32mINFO[0m] error: cannot open Packages database in /var/lib/rpm
* 2023-01-30 02:22:18 (3912) [[32mINFO[0m] CRITICAL:yum.main:
* 2023-01-30 02:22:18 (3912) [[32mINFO[0m] 
* 2023-01-30 02:22:18 (3912) [[32mINFO[0m] Error: rpmdb open failed
* 2023-01-30 02:22:18 (3912) [[32mINFO[0m] (XID xfv7dj) “/usr/bin/yum” reported error code “1” when it ended: 
* 2023-01-30 02:22:31 (3912) [[32mINFO[0m] E Sysup: Needed system packages were not installed: ImageMagick, aspell, at, autoconf, automake, bind, bind-devel, bind-libs, bind-utils, binutils, bison, boost-program-options, boost-serialization, bzip2, cairo, compat-db, coreutils, cpio, cpp, crontabs, curl, dpkg, e2fsprogs, e2fsprogs-devel, ea-cpanel-tools, ea-profiles-cpanel, expat, expat-devel, file, flex, fontconfig, freetype, ftp, gawk, gcc, gcc-c++, gd, gd-devel, gd-progs, gdbm, gdbm-devel, gettext, gettext-devel, ghostscript, giflib, glib2, glibc-devel, glibc-static, gmp, gnupg2, grubby, gzip, hunspell, hunspell-en, initscripts, iptables, json-c, kernel-headers, krb5-devel, less, libX11-devel, libXpm, libXpm-devel, libaio, libaio-devel, libdb, libevent, libgcc, libgomp, libicu, libidn, libidn-devel, libjpeg-turbo, libjpeg-turbo-devel, libmount, libpcap, libpng, libpng-devel, libstdc++, libstdc++-devel, libtiff, libtiff-devel, libtool, libtool-ltdl, libtool-ltdl-devel, libwmf, libxml2, libxml2-devel, libxslt, libxslt-devel, libzip, lsof, make, nano, ncurses, ncurses-devel, ncurses-term, net-tools, nscd, openssh, openssh-clients, openssh-server, openssl, openssl-devel, pam, pam-devel, pango, passwd, patch, pcre, pcre2, perl-CPAN, perl-Expect, perl-ExtUtils-MakeMaker, perl-IO-Tty, perl-JSON-XS, perl-Module-Build, perl-Try-Tiny, perl-YAML-Syck, perl-core, perl-devel, perl-libwww-perl, perl-local-lib, pixman, popt, procps-ng, psmisc, python, python-devel, python-docs, python-setuptools, python-tools, quota, quota-devel, rdate, rsync, sed, shadow-utils, smartmontools, strace, sysstat, tar, tcp_wrappers-devel, traceroute, unzip, urw-fonts, wget, which, xz, yum-plugin-universal-hooks, yum-utils, zip, zlib, zlib-devel
* 2023-01-30 02:22:31 (3929) [[32mINFO[0m] 
* 2023-01-30 02:22:31 (3410) [[33mWARN[0m] /scripts/sysup failed, please fix it and rerun it before upgrading.
* 2023-01-30 02:22:31 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-30 02:22:32 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-30 02:22:32 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/q88bAKh2vM/ea_profile.json
* 2023-01-30 02:22:34 (2694) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/q88bAKh2vM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 1644.
* 2023-01-30 02:22:34 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-01-31 02:21:39 (3552) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-01-31 02:21:42 (3553) [[31mERROR[0m] http://103.101.161.235/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/f0c0f842237bc5eaca73ff553bfdeb6b7920420066150151b48e085a2ec2362e-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/ffb302d165c8adc9fbdd86f3448a839bf2a66d23487f2c666bdb1964d2fb9b4f-filelists.sqlite.bz2: [Errno 12] Timeout on https://repo.extreme-ix.org/epel/7/x86_64/repodata/ffb302d165c8adc9fbdd86f3448a839bf2a66d23487f2c666bdb1964d2fb9b4f-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirror.natro.com/centos/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on http://mirror.natro.com/centos/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://centos.vargonen.com/centos/7.9.2009/updates/x86_64/repodata/63df43ab49ba655c87dd0ee922c8381202d1824907f60340c3c77d2bf2bfaabb-primary.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
Trying other mirror.
http://mirror.radoreservers.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.radoreservers.com/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')
Trying other mirror.
http://mirror.centos.jt.iq/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on http://mirror.centos.jt.iq/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror.sabay.com.kh/epel/7/x86_64/repodata/b23e657d0d11863eab2ce9643cc0af77b20d2ad7d3e38d1ec50782829e5b6810-updateinfo.xml.bz2: [Errno 12] Timeout on https://mirror.sabay.com.kh/epel/7/x86_64/repodata/b23e657d0d11863eab2ce9643cc0af77b20d2ad7d3e38d1ec50782829e5b6810-updateinfo.xml.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
* 2023-01-31 02:21:42 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-01-31 02:21:43 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-01-31 02:21:43 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-01-31 02:21:43 (3898) [[32mINFO[0m] 
* 2023-01-31 02:21:43 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-31 02:21:43 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-01-31 02:21:43 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-01-31 02:21:43 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-01-31 02:21:44 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-01-31 02:21:44 (3929) [[32mINFO[0m] 
* 2023-01-31 02:21:44 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-01-31 02:21:44 (3898) [[32mINFO[0m] 
* 2023-01-31 02:22:05 (3912) [[32mINFO[0m] http://118.88.24.67/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/b581bf8bf1ad82e71ed12073db679f5253256410bf48b3ca193a2eab1504f83b-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
* 2023-01-31 02:22:05 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-01-31 02:22:51 (3912) [[32mINFO[0m] 
* 2023-01-31 02:22:51 (3912) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-01-31 02:22:51 (3929) [[32mINFO[0m] 
* 2023-01-31 02:22:51 (3393) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-31 02:22:51 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-31 02:22:51 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-31 02:22:51 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RJ2vJTlxK_/ea_profile.json
* 2023-01-31 02:22:52 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/RJ2vJTlxK_/ea_profile.json
* 2023-01-31 02:22:52 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-01-31 02:22:54 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-01 02:20:26 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-01 02:20:26 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-01 02:20:26 (3898) [[32mINFO[0m] 
* 2023-02-01 02:20:28 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-01 02:20:29 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-01 02:20:29 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-01 02:20:29 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-01 02:20:29 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-02-01 02:20:29 (3929) [[32mINFO[0m] 
* 2023-02-01 02:20:29 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-01 02:20:29 (3898) [[32mINFO[0m] 
* 2023-02-01 02:21:29 (3912) [[32mINFO[0m] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/7a5574a1e3cdbef170c0315d92d961509411fce09356e652ff788cf3cf7f4981-primary.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/7a5574a1e3cdbef170c0315d92d961509411fce09356e652ff788cf3cf7f4981-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-02-01 02:21:29 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-01 02:21:56 (3912) [[32mINFO[0m] http://103.48.119.120/cpanelsync/repos/CentOS/7/EA4/repodata/b00aa0b57c2bfa89eb0d64192caa50ab66b9afe65c32e2e605ec48b1eb5c0471-primary.sqlite.bz2: [Errno 12] Timeout on http://103.48.119.120/cpanelsync/repos/CentOS/7/EA4/repodata/b00aa0b57c2bfa89eb0d64192caa50ab66b9afe65c32e2e605ec48b1eb5c0471-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-02-01 02:21:56 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-01 02:22:56 (3912) [[32mINFO[0m] http://45.228.65.220/cpanelsync/repos/CentOS/7/EA4/repodata/b00aa0b57c2bfa89eb0d64192caa50ab66b9afe65c32e2e605ec48b1eb5c0471-primary.sqlite.bz2: [Errno 12] Timeout on http://45.228.65.220/cpanelsync/repos/CentOS/7/EA4/repodata/b00aa0b57c2bfa89eb0d64192caa50ab66b9afe65c32e2e605ec48b1eb5c0471-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-02-01 02:22:56 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-01 02:23:02 (3912) [[32mINFO[0m] http://185.125.185.32/cpanelsync/repos/CentOS/7/EA4/repodata/b00aa0b57c2bfa89eb0d64192caa50ab66b9afe65c32e2e605ec48b1eb5c0471-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-02-01 02:23:02 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-01 02:23:57 (3929) [[32mINFO[0m] 
* 2023-02-01 02:23:57 (3393) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-01 02:23:57 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-01 02:23:57 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-01 02:23:57 (3898) [[32mINFO[0m] 
* 2023-02-01 02:23:58 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-01 02:24:18 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot kernel)
* 2023-02-01 02:24:19 (3912) [[32mINFO[0m] error: rpmdb: BDB0113 Thread/process 26929/140642215106368 failed: BDB1507 Thread died in Berkeley DB library
* 2023-02-01 02:24:19 (3912) [[32mINFO[0m] error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
* 2023-02-01 02:24:19 (3912) [[32mINFO[0m] error: cannot open Packages index using db5 -  (-30973)
* 2023-02-01 02:24:19 (3912) [[32mINFO[0m] error: cannot open Packages database in /var/lib/rpm
* 2023-02-01 02:24:19 (3912) [[32mINFO[0m] CRITICAL:yum.main:
* 2023-02-01 02:24:19 (3912) [[32mINFO[0m] 
* 2023-02-01 02:24:19 (3912) [[32mINFO[0m] Error: rpmdb open failed
* 2023-02-01 02:24:19 (3912) [[32mINFO[0m] (XID 2x9mp8) “/usr/bin/yum” reported error code “1” when it ended: 
* 2023-02-01 02:24:35 (3912) [[32mINFO[0m] E Sysup: Needed system packages were not installed: ImageMagick, aspell, at, autoconf, automake, bind, bind-devel, bind-libs, bind-utils, binutils, bison, boost-program-options, boost-serialization, bzip2, cairo, compat-db, coreutils, cpio, cpp, crontabs, curl, dpkg, e2fsprogs, e2fsprogs-devel, ea-cpanel-tools, ea-profiles-cpanel, expat, expat-devel, file, flex, fontconfig, freetype, ftp, gawk, gcc, gcc-c++, gd, gd-devel, gd-progs, gdbm, gdbm-devel, gettext, gettext-devel, ghostscript, giflib, glib2, glibc-devel, glibc-static, gmp, gnupg2, grubby, gzip, hunspell, hunspell-en, initscripts, iptables, json-c, kernel-headers, krb5-devel, less, libX11-devel, libXpm, libXpm-devel, libaio, libaio-devel, libdb, libevent, libgcc, libgomp, libicu, libidn, libidn-devel, libjpeg-turbo, libjpeg-turbo-devel, libmount, libpcap, libpng, libpng-devel, libstdc++, libstdc++-devel, libtiff, libtiff-devel, libtool, libtool-ltdl, libtool-ltdl-devel, libwmf, libxml2, libxml2-devel, libxslt, libxslt-devel, libzip, lsof, make, nano, ncurses, ncurses-devel, ncurses-term, net-tools, nscd, openssh, openssh-clients, openssh-server, openssl, openssl-devel, pam, pam-devel, pango, passwd, patch, pcre, pcre2, perl-CPAN, perl-Expect, perl-ExtUtils-MakeMaker, perl-IO-Tty, perl-JSON-XS, perl-Module-Build, perl-Try-Tiny, perl-YAML-Syck, perl-core, perl-devel, perl-libwww-perl, perl-local-lib, pixman, popt, procps-ng, psmisc, python, python-devel, python-docs, python-setuptools, python-tools, quota, quota-devel, rdate, rsync, sed, shadow-utils, smartmontools, strace, sysstat, tar, tcp_wrappers-devel, traceroute, unzip, urw-fonts, wget, which, xz, yum-plugin-universal-hooks, yum-utils, zip, zlib, zlib-devel
* 2023-02-01 02:24:35 (3929) [[32mINFO[0m] 
* 2023-02-01 02:24:35 (3410) [[33mWARN[0m] /scripts/sysup failed, please fix it and rerun it before upgrading.
* 2023-02-01 02:24:35 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-01 02:24:35 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-01 02:24:35 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/elqXyPVCWt/ea_profile.json
* 2023-02-01 02:24:36 (2694) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/elqXyPVCWt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 1644.
* 2023-02-01 02:24:36 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-01 02:24:40 (3552) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-02-01 02:24:40 (3553) [[31mERROR[0m] error: rpmdb: BDB0113 Thread/process 26929/140642215106368 failed: BDB1507 Thread died in Berkeley DB library
error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db5 -  (-30973)
error: cannot open Packages database in /var/lib/rpm
CRITICAL:yum.main:

Error: rpmdb open failed
* 2023-02-01 02:24:40 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-02-01 02:24:40 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-01 02:24:40 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-01 02:24:40 (3898) [[32mINFO[0m] 
* 2023-02-01 02:24:40 (3912) [[32mINFO[0m] error: rpmdb: BDB0113 Thread/process 26929/140642215106368 failed: BDB1507 Thread died in Berkeley DB library
* 2023-02-01 02:24:40 (3912) [[32mINFO[0m] error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
* 2023-02-01 02:24:40 (3912) [[32mINFO[0m] error: cannot open Packages index using db5 -  (-30973)
* 2023-02-01 02:24:40 (3912) [[32mINFO[0m] error: cannot open Packages database in /var/lib/rpm
* 2023-02-01 02:24:40 (3912) [[32mINFO[0m] CRITICAL:yum.main:
* 2023-02-01 02:24:40 (3912) [[32mINFO[0m] 
* 2023-02-01 02:24:40 (3912) [[32mINFO[0m] Error: rpmdb open failed
* 2023-02-01 02:24:40 (3929) [[32mINFO[0m] 
* 2023-02-01 02:24:40 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-01 02:24:40 (3898) [[32mINFO[0m] 
* 2023-02-01 02:24:41 (3912) [[32mINFO[0m] error: rpmdb: BDB0113 Thread/process 26929/140642215106368 failed: BDB1507 Thread died in Berkeley DB library
* 2023-02-01 02:24:41 (3912) [[32mINFO[0m] error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
* 2023-02-01 02:24:41 (3912) [[32mINFO[0m] error: cannot open Packages index using db5 -  (-30973)
* 2023-02-01 02:24:41 (3912) [[32mINFO[0m] error: cannot open Packages database in /var/lib/rpm
* 2023-02-01 02:24:41 (3912) [[32mINFO[0m] CRITICAL:yum.main:
* 2023-02-01 02:24:41 (3912) [[32mINFO[0m] 
* 2023-02-01 02:24:41 (3912) [[32mINFO[0m] Error: rpmdb open failed
* 2023-02-01 02:24:41 (3929) [[32mINFO[0m] 
* 2023-02-01 02:24:41 (3393) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-01 02:24:41 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-01 02:24:41 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-01 02:24:41 (3898) [[32mINFO[0m] 
* 2023-02-01 02:24:41 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-01 02:24:59 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot kernel)
* 2023-02-01 02:25:00 (3912) [[32mINFO[0m] error: rpmdb: BDB0113 Thread/process 26929/140642215106368 failed: BDB1507 Thread died in Berkeley DB library
* 2023-02-01 02:25:00 (3912) [[32mINFO[0m] error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
* 2023-02-01 02:25:00 (3912) [[32mINFO[0m] error: cannot open Packages index using db5 -  (-30973)
* 2023-02-01 02:25:00 (3912) [[32mINFO[0m] error: cannot open Packages database in /var/lib/rpm
* 2023-02-01 02:25:00 (3912) [[32mINFO[0m] CRITICAL:yum.main:
* 2023-02-01 02:25:00 (3912) [[32mINFO[0m] 
* 2023-02-01 02:25:00 (3912) [[32mINFO[0m] Error: rpmdb open failed
* 2023-02-01 02:25:00 (3912) [[32mINFO[0m] (XID f9u6gf) “/usr/bin/yum” reported error code “1” when it ended: 
* 2023-02-01 02:25:18 (3912) [[32mINFO[0m] E Sysup: Needed system packages were not installed: ImageMagick, aspell, at, autoconf, automake, bind, bind-devel, bind-libs, bind-utils, binutils, bison, boost-program-options, boost-serialization, bzip2, cairo, compat-db, coreutils, cpio, cpp, crontabs, curl, dpkg, e2fsprogs, e2fsprogs-devel, ea-cpanel-tools, ea-profiles-cpanel, expat, expat-devel, file, flex, fontconfig, freetype, ftp, gawk, gcc, gcc-c++, gd, gd-devel, gd-progs, gdbm, gdbm-devel, gettext, gettext-devel, ghostscript, giflib, glib2, glibc-devel, glibc-static, gmp, gnupg2, grubby, gzip, hunspell, hunspell-en, initscripts, iptables, json-c, kernel-headers, krb5-devel, less, libX11-devel, libXpm, libXpm-devel, libaio, libaio-devel, libdb, libevent, libgcc, libgomp, libicu, libidn, libidn-devel, libjpeg-turbo, libjpeg-turbo-devel, libmount, libpcap, libpng, libpng-devel, libstdc++, libstdc++-devel, libtiff, libtiff-devel, libtool, libtool-ltdl, libtool-ltdl-devel, libwmf, libxml2, libxml2-devel, libxslt, libxslt-devel, libzip, lsof, make, nano, ncurses, ncurses-devel, ncurses-term, net-tools, nscd, openssh, openssh-clients, openssh-server, openssl, openssl-devel, pam, pam-devel, pango, passwd, patch, pcre, pcre2, perl-CPAN, perl-Expect, perl-ExtUtils-MakeMaker, perl-IO-Tty, perl-JSON-XS, perl-Module-Build, perl-Try-Tiny, perl-YAML-Syck, perl-core, perl-devel, perl-libwww-perl, perl-local-lib, pixman, popt, procps-ng, psmisc, python, python-devel, python-docs, python-setuptools, python-tools, quota, quota-devel, rdate, rsync, sed, shadow-utils, smartmontools, strace, sysstat, tar, tcp_wrappers-devel, traceroute, unzip, urw-fonts, wget, which, xz, yum-plugin-universal-hooks, yum-utils, zip, zlib, zlib-devel
* 2023-02-01 02:25:18 (3929) [[32mINFO[0m] 
* 2023-02-01 02:25:18 (3410) [[33mWARN[0m] /scripts/sysup failed, please fix it and rerun it before upgrading.
* 2023-02-01 02:25:18 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-01 02:25:18 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-01 02:25:18 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LrsmhOH8de/ea_profile.json
* 2023-02-01 02:25:23 (2694) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LrsmhOH8de/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 1644.
* 2023-02-01 02:25:23 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-01 16:29:35 (3552) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-02-01 16:29:35 (3553) [[31mERROR[0m] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/a744cba1413048236d1169deb83e1e6f8eb5c54eafe2fdddea20ed6d0d34cad0-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://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/da6521de2b1576ce7d6342e6c13af9694e9ca2c21a3f94aee382dd5649593e44-prestodelta.xml.gz: [Errno 12] Timeout on http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/da6521de2b1576ce7d6342e6c13af9694e9ca2c21a3f94aee382dd5649593e44-prestodelta.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/da6521de2b1576ce7d6342e6c13af9694e9ca2c21a3f94aee382dd5649593e44-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/da6521de2b1576ce7d6342e6c13af9694e9ca2c21a3f94aee382dd5649593e44-prestodelta.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirror.dimensi.cloud/epel/7/x86_64/repodata/a744cba1413048236d1169deb83e1e6f8eb5c54eafe2fdddea20ed6d0d34cad0-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.dimensi.cloud/epel/7/x86_64/repodata/a744cba1413048236d1169deb83e1e6f8eb5c54eafe2fdddea20ed6d0d34cad0-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/a744cba1413048236d1169deb83e1e6f8eb5c54eafe2fdddea20ed6d0d34cad0-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/da6521de2b1576ce7d6342e6c13af9694e9ca2c21a3f94aee382dd5649593e44-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
* 2023-02-01 16:29:35 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-02-01 16:29:35 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-01 16:29:35 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-01 16:29:35 (3898) [[32mINFO[0m] 
* 2023-02-01 16:29:36 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-01 16:29:36 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-01 16:29:36 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-01 16:29:36 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-01 16:29:36 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-02-01 16:29:36 (3929) [[32mINFO[0m] 
* 2023-02-01 16:29:36 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-01 16:29:36 (3898) [[32mINFO[0m] 
* 2023-02-01 16:30:40 (3912) [[32mINFO[0m] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/a9c7a8cbffb5e5c07cbf31397bf11d9f7755e96c72ce897e04dba556dd4cc0eb-comps-Everything.x86_64.xml.gz: [Errno 12] Timeout on https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/a9c7a8cbffb5e5c07cbf31397bf11d9f7755e96c72ce897e04dba556dd4cc0eb-comps-Everything.x86_64.xml.gz: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
* 2023-02-01 16:30:40 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-01 16:30:41 (3912) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/46933cf6ed3bed7970a6084f3413bc1135bd471db766e3488856e899890f3dcf-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-02-01 16:30:41 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-01 16:30:41 (3912) [[32mINFO[0m] To address this issue please refer to the below wiki article 
* 2023-02-01 16:30:41 (3912) [[32mINFO[0m] 
* 2023-02-01 16:30:41 (3912) [[32mINFO[0m] https://wiki.centos.org/yum-errors
* 2023-02-01 16:30:41 (3912) [[32mINFO[0m] 
* 2023-02-01 16:30:41 (3912) [[32mINFO[0m] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2023-02-01 16:30:41 (3912) [[32mINFO[0m] 
* 2023-02-01 16:31:10 (3912) [[32mINFO[0m] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/4899a09571633d562f709de3f2b36c29bebcc97648b267086b712fc01dd48b8a-updateinfo.xml.bz2: [Errno 12] Timeout on https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/4899a09571633d562f709de3f2b36c29bebcc97648b267086b712fc01dd48b8a-updateinfo.xml.bz2: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
* 2023-02-01 16:31:10 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-01 16:31:11 (3912) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/4899a09571633d562f709de3f2b36c29bebcc97648b267086b712fc01dd48b8a-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-02-01 16:31:11 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-01 16:31:20 (3912) [[32mINFO[0m] http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/46933cf6ed3bed7970a6084f3413bc1135bd471db766e3488856e899890f3dcf-primary.sqlite.bz2: [Errno 12] Timeout on http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/46933cf6ed3bed7970a6084f3413bc1135bd471db766e3488856e899890f3dcf-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-02-01 16:31:20 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-01 16:32:07 (3912) [[32mINFO[0m] http://mirror.dimensi.cloud/epel/7/x86_64/repodata/46933cf6ed3bed7970a6084f3413bc1135bd471db766e3488856e899890f3dcf-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.dimensi.cloud/epel/7/x86_64/repodata/46933cf6ed3bed7970a6084f3413bc1135bd471db766e3488856e899890f3dcf-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-02-01 16:32:07 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-01 16:32:43 (3912) [[32mINFO[0m] https://repo.extreme-ix.org/epel/7/x86_64/repodata/46933cf6ed3bed7970a6084f3413bc1135bd471db766e3488856e899890f3dcf-primary.sqlite.bz2: [Errno 12] Timeout on https://repo.extreme-ix.org/epel/7/x86_64/repodata/46933cf6ed3bed7970a6084f3413bc1135bd471db766e3488856e899890f3dcf-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-02-01 16:32:43 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-01 16:33:23 (3929) [[32mINFO[0m] 
* 2023-02-01 16:33:23 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-01 16:33:23 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-01 16:33:23 (3898) [[32mINFO[0m] 
* 2023-02-01 16:33:24 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-01 16:33:25 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-01 16:33:25 (3929) [[32mINFO[0m] 
* 2023-02-01 16:33:25 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-01 16:33:25 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/E7Zs4LwhJR/ea_profile.json
* 2023-02-01 16:33:27 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/E7Zs4LwhJR/ea_profile.json
* 2023-02-01 16:33:27 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-01 16:33:30 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-02 02:15:00 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-02 02:15:00 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-02 02:15:00 (3898) [[32mINFO[0m] 
* 2023-02-02 02:15:01 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-02 02:15:01 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-02 02:15:03 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-02 02:15:03 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-02 02:15:03 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-02-02 02:15:03 (3929) [[32mINFO[0m] 
* 2023-02-02 02:15:03 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-02 02:15:03 (3898) [[32mINFO[0m] 
* 2023-02-02 02:15:26 (3912) [[32mINFO[0m] http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/b1620cbc47f9e36cdc9e0c01b97cd9d73bf1c40b0df39c20f95eb23c6ddd4ad2-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
* 2023-02-02 02:15:26 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-02 02:15:34 (3912) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/46933cf6ed3bed7970a6084f3413bc1135bd471db766e3488856e899890f3dcf-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-02-02 02:15:34 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-02 02:15:34 (3912) [[32mINFO[0m] To address this issue please refer to the below wiki article 
* 2023-02-02 02:15:34 (3912) [[32mINFO[0m] 
* 2023-02-02 02:15:34 (3912) [[32mINFO[0m] https://wiki.centos.org/yum-errors
* 2023-02-02 02:15:34 (3912) [[32mINFO[0m] 
* 2023-02-02 02:15:34 (3912) [[32mINFO[0m] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2023-02-02 02:15:34 (3912) [[32mINFO[0m] 
* 2023-02-02 02:16:02 (3912) [[32mINFO[0m] http://31.22.112.31/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/b581bf8bf1ad82e71ed12073db679f5253256410bf48b3ca193a2eab1504f83b-primary.sqlite.bz2: [Errno 12] Timeout on http://31.22.112.31/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/b581bf8bf1ad82e71ed12073db679f5253256410bf48b3ca193a2eab1504f83b-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-02-02 02:16:02 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-02 02:16:03 (3912) [[32mINFO[0m] http://208.100.0.204/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/b581bf8bf1ad82e71ed12073db679f5253256410bf48b3ca193a2eab1504f83b-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-02-02 02:16:03 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-02 02:16:23 (3929) [[32mINFO[0m] 
* 2023-02-02 02:16:23 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-02 02:16:23 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-02 02:16:23 (3898) [[32mINFO[0m] 
* 2023-02-02 02:16:23 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-02 02:16:25 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-02 02:16:25 (3929) [[32mINFO[0m] 
* 2023-02-02 02:16:25 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-02 02:16:25 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yAEvrVNmgH/ea_profile.json
* 2023-02-02 02:16:26 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/yAEvrVNmgH/ea_profile.json
* 2023-02-02 02:16:26 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-02 02:16:28 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-02 10:29:16 (3552) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-02-02 10:29:16 (3553) [[31mERROR[0m] http://centos.vargonen.com/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/d8929a10bc93d0e5cd9adfc1edad2a13b1026e359475dcf2fbd89d0f1041da4c-other.sqlite.bz2: [Errno 12] Timeout on http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/d8929a10bc93d0e5cd9adfc1edad2a13b1026e359475dcf2fbd89d0f1041da4c-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://istanbul.centos-mirror.guzel.net.tr/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on http://istanbul.centos-mirror.guzel.net.tr/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-02-02 10:29:16 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-02-02 10:29:16 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-02 10:29:16 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-02 10:29:16 (3898) [[32mINFO[0m] 
* 2023-02-02 10:29:17 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-02 10:29:17 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-02 10:29:17 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-02 10:29:17 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-02 10:29:17 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-02-02 10:29:17 (3929) [[32mINFO[0m] 
* 2023-02-02 10:29:17 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-02 10:29:17 (3898) [[32mINFO[0m] 
* 2023-02-02 10:29:37 (3912) [[32mINFO[0m] http://103.72.162.35/cpanelsync/repos/CentOS/7/EA4/repodata/repomd.xml: [Errno 14] curl#52 - "Empty reply from server"
* 2023-02-02 10:29:37 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-02 10:30:17 (3912) [[32mINFO[0m] http://mirror.alastyr.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.alastyr.com/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-02-02 10:30:17 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-02 10:30:26 (3912) [[32mINFO[0m] http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/b1620cbc47f9e36cdc9e0c01b97cd9d73bf1c40b0df39c20f95eb23c6ddd4ad2-primary.sqlite.bz2: [Errno 12] Timeout on http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/b1620cbc47f9e36cdc9e0c01b97cd9d73bf1c40b0df39c20f95eb23c6ddd4ad2-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-02-02 10:30:26 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-02 10:30:45 (3912) [[32mINFO[0m] http://102.22.80.80/cpanelsync/repos/CentOS/7/EA4/repodata/b1620cbc47f9e36cdc9e0c01b97cd9d73bf1c40b0df39c20f95eb23c6ddd4ad2-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-02-02 10:30:45 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-02 10:30:53 (3912) [[32mINFO[0m] http://centos.vargonen.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://centos.vargonen.com/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-02-02 10:30:53 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-02 10:31:19 (3912) [[32mINFO[0m] http://mirrors.nipa.cloud/epel/7/x86_64/repodata/46933cf6ed3bed7970a6084f3413bc1135bd471db766e3488856e899890f3dcf-primary.sqlite.bz2: [Errno 12] Timeout on http://mirrors.nipa.cloud/epel/7/x86_64/repodata/46933cf6ed3bed7970a6084f3413bc1135bd471db766e3488856e899890f3dcf-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-02-02 10:31:19 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-02 10:32:14 (3912) [[32mINFO[0m] https://mirror.yer.az/fedora-epel/7/x86_64/repodata/46933cf6ed3bed7970a6084f3413bc1135bd471db766e3488856e899890f3dcf-primary.sqlite.bz2: [Errno 12] Timeout on https://mirror.yer.az/fedora-epel/7/x86_64/repodata/46933cf6ed3bed7970a6084f3413bc1135bd471db766e3488856e899890f3dcf-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-02-02 10:32:14 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-02 10:32:48 (3929) [[32mINFO[0m] 
* 2023-02-02 10:32:48 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-02 10:32:48 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-02 10:32:48 (3898) [[32mINFO[0m] 
* 2023-02-02 10:32:48 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-02 10:32:50 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-02 10:32:50 (3929) [[32mINFO[0m] 
* 2023-02-02 10:32:51 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-02 10:32:55 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/udluigo5OG/ea_profile.json
* 2023-02-02 10:32:57 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/udluigo5OG/ea_profile.json
* 2023-02-02 10:32:57 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-02 10:32:59 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-02 11:01:59 (3552) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-02-02 11:01:59 (3553) [[31mERROR[0m] https://mirror.yer.az/fedora-epel/7/x86_64/repodata/13690433f11b20f2189f64f2936dcfd506b1cc0a7834cd39d2767923d1ab6bb2-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://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/6dd7558ff11298ca01cf701e7778efa430918edaee45edbac5f245e08b54ca04-prestodelta.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirror.yer.az/fedora-epel/7/x86_64/repodata/6dd7558ff11298ca01cf701e7778efa430918edaee45edbac5f245e08b54ca04-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/13690433f11b20f2189f64f2936dcfd506b1cc0a7834cd39d2767923d1ab6bb2-other.sqlite.bz2: [Errno 12] Timeout on https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/13690433f11b20f2189f64f2936dcfd506b1cc0a7834cd39d2767923d1ab6bb2-other.sqlite.bz2: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/13690433f11b20f2189f64f2936dcfd506b1cc0a7834cd39d2767923d1ab6bb2-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirror.sabay.com.kh/epel/7/x86_64/repodata/13690433f11b20f2189f64f2936dcfd506b1cc0a7834cd39d2767923d1ab6bb2-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-jp.misakamikoto.network/fedora-epel/7/x86_64/repodata/6dd7558ff11298ca01cf701e7778efa430918edaee45edbac5f245e08b54ca04-prestodelta.xml.gz: [Errno 12] Timeout on https://mirror-jp.misakamikoto.network/fedora-epel/7/x86_64/repodata/6dd7558ff11298ca01cf701e7778efa430918edaee45edbac5f245e08b54ca04-prestodelta.xml.gz: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
Trying other mirror.
https://mirror.sabay.com.kh/epel/7/x86_64/repodata/6dd7558ff11298ca01cf701e7778efa430918edaee45edbac5f245e08b54ca04-prestodelta.xml.gz: [Errno 12] Timeout on https://mirror.sabay.com.kh/epel/7/x86_64/repodata/6dd7558ff11298ca01cf701e7778efa430918edaee45edbac5f245e08b54ca04-prestodelta.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://epel.mirror.angkasa.id/pub/epel/7/x86_64/repodata/13690433f11b20f2189f64f2936dcfd506b1cc0a7834cd39d2767923d1ab6bb2-other.sqlite.bz2: [Errno 12] Timeout on http://epel.mirror.angkasa.id/pub/epel/7/x86_64/repodata/13690433f11b20f2189f64f2936dcfd506b1cc0a7834cd39d2767923d1ab6bb2-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror-jp.misakamikoto.network/fedora-epel/7/x86_64/repodata/13690433f11b20f2189f64f2936dcfd506b1cc0a7834cd39d2767923d1ab6bb2-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/6dd7558ff11298ca01cf701e7778efa430918edaee45edbac5f245e08b54ca04-prestodelta.xml.gz: [Errno 12] Timeout on https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/6dd7558ff11298ca01cf701e7778efa430918edaee45edbac5f245e08b54ca04-prestodelta.xml.gz: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')
Trying other mirror.
https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/6dd7558ff11298ca01cf701e7778efa430918edaee45edbac5f245e08b54ca04-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
* 2023-02-02 11:01:59 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-02-02 11:02:00 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-02 11:02:00 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-02 11:02:00 (3898) [[32mINFO[0m] 
* 2023-02-02 11:02:00 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-02 11:02:00 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-02 11:02:00 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-02 11:02:00 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-02 11:02:00 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-02-02 11:02:00 (3929) [[32mINFO[0m] 
* 2023-02-02 11:02:01 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-02 11:02:01 (3898) [[32mINFO[0m] 
* 2023-02-02 11:02:46 (3912) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/a9c7a8cbffb5e5c07cbf31397bf11d9f7755e96c72ce897e04dba556dd4cc0eb-comps-Everything.x86_64.xml.gz: [Errno 12] Timeout on http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/a9c7a8cbffb5e5c07cbf31397bf11d9f7755e96c72ce897e04dba556dd4cc0eb-comps-Everything.x86_64.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-02-02 11:02:46 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-02 11:02:47 (3912) [[32mINFO[0m] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/46933cf6ed3bed7970a6084f3413bc1135bd471db766e3488856e899890f3dcf-primary.sqlite.bz2: [Errno 12] Timeout on https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/46933cf6ed3bed7970a6084f3413bc1135bd471db766e3488856e899890f3dcf-primary.sqlite.bz2: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
* 2023-02-02 11:02:47 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-02 11:03:43 (3912) [[32mINFO[0m] https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/46933cf6ed3bed7970a6084f3413bc1135bd471db766e3488856e899890f3dcf-primary.sqlite.bz2: [Errno 12] Timeout on https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/46933cf6ed3bed7970a6084f3413bc1135bd471db766e3488856e899890f3dcf-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-02-02 11:03:43 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-02 11:04:43 (3912) [[32mINFO[0m] https://mirror.yer.az/fedora-epel/7/x86_64/repodata/46933cf6ed3bed7970a6084f3413bc1135bd471db766e3488856e899890f3dcf-primary.sqlite.bz2: [Errno 12] Timeout on https://mirror.yer.az/fedora-epel/7/x86_64/repodata/46933cf6ed3bed7970a6084f3413bc1135bd471db766e3488856e899890f3dcf-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-02-02 11:04:43 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-02 11:05:18 (3929) [[32mINFO[0m] 
* 2023-02-02 11:05:18 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-02 11:05:18 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-02 11:05:18 (3898) [[32mINFO[0m] 
* 2023-02-02 11:05:18 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-02 11:05:21 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-02 11:05:21 (3929) [[32mINFO[0m] 
* 2023-02-02 11:05:21 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-02 11:05:21 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mTp9WspqlO/ea_profile.json
* 2023-02-02 11:05:23 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/mTp9WspqlO/ea_profile.json
* 2023-02-02 11:05:23 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-02 11:05:24 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-03 02:16:43 (3552) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-02-03 02:16:43 (3553) [[31mERROR[0m] http://118.88.24.67/cpanelsync/repos/CentOS/7/EA4/repodata/17d32915a32497c508a3e4900d29bc443f40e6d527d978f476e5f0d5a8d13d9a-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://centos.vargonen.com/centos/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
Trying other mirror.
http://mirror.bursabil.com.tr/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2a04:3880:0:16::205: Network is unreachable"
Trying other mirror.
http://mirror.bursabil.com.tr/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.bursabil.com.tr/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')
Trying other mirror.
http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/0f452570f8c6f45b84f99de05e93d9ec72538faeff53fdc5bc787b3fcfae877d-other.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/0f452570f8c6f45b84f99de05e93d9ec72538faeff53fdc5bc787b3fcfae877d-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://centos.vargonen.com/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
Trying other mirror.
http://208.74.123.61/cpanelsync/repos/CentOS/7/EA4/repodata/0f452570f8c6f45b84f99de05e93d9ec72538faeff53fdc5bc787b3fcfae877d-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://centos.turhost.com/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://centos.turhost.com/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')
Trying other mirror.
http://mirror.centos.jt.iq/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.centos.jt.iq/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.
http://epel.mirror.angkasa.id/pub/epel/7/x86_64/repodata/23a3116d536a5ab4f53c0d87263fc6fefda7b655a166200e3ef5f4b8e0a04d11-filelists.sqlite.bz2: [Errno 12] Timeout on http://epel.mirror.angkasa.id/pub/epel/7/x86_64/repodata/23a3116d536a5ab4f53c0d87263fc6fefda7b655a166200e3ef5f4b8e0a04d11-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
* 2023-02-03 02:16:43 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-02-03 02:16:44 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-03 02:16:44 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-03 02:16:44 (3898) [[32mINFO[0m] 
* 2023-02-03 02:16:44 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-03 02:16:44 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-03 02:16:44 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-03 02:16:56 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-03 02:16:56 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-02-03 02:16:56 (3929) [[32mINFO[0m] 
* 2023-02-03 02:16:56 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-03 02:16:56 (3898) [[32mINFO[0m] 
* 2023-02-03 02:17:29 (3929) [[32mINFO[0m] 
* 2023-02-03 02:17:29 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-03 02:17:29 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-03 02:17:29 (3898) [[32mINFO[0m] 
* 2023-02-03 02:17:29 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-03 02:17:30 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-03 02:17:30 (3929) [[32mINFO[0m] 
* 2023-02-03 02:17:30 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-03 02:17:31 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xu97Ia8lVm/ea_profile.json
* 2023-02-03 02:17:32 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/xu97Ia8lVm/ea_profile.json
* 2023-02-03 02:17:32 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-03 02:17:34 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-03 16:01:06 (3552) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-02-03 16:01:06 (3553) [[31mERROR[0m] http://istanbul.centos-mirror.guzel.net.tr/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://istanbul.centos-mirror.guzel.net.tr/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirror.verinomi.com/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.verinomi.com/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-02-03 16:01:06 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-02-03 16:01:07 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-03 16:01:07 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-03 16:01:07 (3898) [[32mINFO[0m] 
* 2023-02-03 16:01:07 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-03 16:01:07 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-03 16:01:07 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-03 16:01:08 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-03 16:01:08 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-02-03 16:01:08 (3929) [[32mINFO[0m] 
* 2023-02-03 16:01:08 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-03 16:01:08 (3898) [[32mINFO[0m] 
* 2023-02-03 16:02:00 (3912) [[32mINFO[0m] http://istanbul.centos-mirror.guzel.net.tr/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on http://istanbul.centos-mirror.guzel.net.tr/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-02-03 16:02:00 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-03 16:02:31 (3929) [[32mINFO[0m] 
* 2023-02-03 16:02:31 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-03 16:02:31 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-03 16:02:31 (3898) [[32mINFO[0m] 
* 2023-02-03 16:02:31 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-03 16:02:32 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-03 16:02:32 (3929) [[32mINFO[0m] 
* 2023-02-03 16:02:32 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-03 16:02:32 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jImNhPKRE7/ea_profile.json
* 2023-02-03 16:02:34 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/jImNhPKRE7/ea_profile.json
* 2023-02-03 16:02:34 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-03 16:02:35 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-04 02:16:09 (3552) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-02-04 02:16:09 (3553) [[31mERROR[0m] http://63.247.64.58/cpanelsync/repos/CentOS/7/EA4/repodata/0f452570f8c6f45b84f99de05e93d9ec72538faeff53fdc5bc787b3fcfae877d-other.sqlite.bz2: [Errno 12] Timeout on http://63.247.64.58/cpanelsync/repos/CentOS/7/EA4/repodata/0f452570f8c6f45b84f99de05e93d9ec72538faeff53fdc5bc787b3fcfae877d-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror-jp.misakamikoto.network/fedora-epel/7/x86_64/repodata/b0e3c93831f386ebdae9e9fa9acddf686d5af86a75ecf2960d7c0eb93afef980-filelists.sqlite.bz2: [Errno 12] Timeout on https://mirror-jp.misakamikoto.network/fedora-epel/7/x86_64/repodata/b0e3c93831f386ebdae9e9fa9acddf686d5af86a75ecf2960d7c0eb93afef980-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/cc9cbaec5aa55e8a12dedb88ad383ff17777cafe4eafdd3616536f401c8952e7-other.sqlite.bz2: [Errno 12] Timeout on https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/cc9cbaec5aa55e8a12dedb88ad383ff17777cafe4eafdd3616536f401c8952e7-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/2b507fb4432d8a64bb70e63020ee477ab5163df5481a257571b678bfdb761845-filelists.sqlite.bz2: [Errno 12] Timeout on http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/2b507fb4432d8a64bb70e63020ee477ab5163df5481a257571b678bfdb761845-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.15.48.49/cpanelsync/repos/CentOS/7/EA4/repodata/2b507fb4432d8a64bb70e63020ee477ab5163df5481a257571b678bfdb761845-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://102.22.80.80/cpanelsync/repos/CentOS/7/EA4/repodata/0f452570f8c6f45b84f99de05e93d9ec72538faeff53fdc5bc787b3fcfae877d-other.sqlite.bz2: [Errno 12] Timeout on http://102.22.80.80/cpanelsync/repos/CentOS/7/EA4/repodata/0f452570f8c6f45b84f99de05e93d9ec72538faeff53fdc5bc787b3fcfae877d-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.15.48.49/cpanelsync/repos/CentOS/7/EA4/repodata/0f452570f8c6f45b84f99de05e93d9ec72538faeff53fdc5bc787b3fcfae877d-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/cc9cbaec5aa55e8a12dedb88ad383ff17777cafe4eafdd3616536f401c8952e7-other.sqlite.bz2: [Errno 12] Timeout on https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/cc9cbaec5aa55e8a12dedb88ad383ff17777cafe4eafdd3616536f401c8952e7-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
* 2023-02-04 02:16:09 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-02-04 02:16:10 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-04 02:16:10 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-04 02:16:10 (3898) [[32mINFO[0m] 
* 2023-02-04 02:16:10 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-04 02:16:10 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-04 02:16:10 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-04 02:16:10 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-04 02:16:11 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-02-04 02:16:11 (3929) [[32mINFO[0m] 
* 2023-02-04 02:16:11 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-04 02:16:11 (3898) [[32mINFO[0m] 
* 2023-02-04 02:17:40 (3912) [[32mINFO[0m] https://mirror.sabay.com.kh/epel/7/x86_64/repodata/f72411285aa44807533d310bd249c37ae95e44ac6b084fe680541c2968301d42-primary.sqlite.bz2: [Errno 12] Timeout on https://mirror.sabay.com.kh/epel/7/x86_64/repodata/f72411285aa44807533d310bd249c37ae95e44ac6b084fe680541c2968301d42-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-02-04 02:17:40 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-04 02:18:27 (3929) [[32mINFO[0m] 
* 2023-02-04 02:18:27 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-04 02:18:27 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-04 02:18:27 (3898) [[32mINFO[0m] 
* 2023-02-04 02:18:27 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-04 02:18:29 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-04 02:18:29 (3929) [[32mINFO[0m] 
* 2023-02-04 02:18:29 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-04 02:18:29 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aLQF6JoRjO/ea_profile.json
* 2023-02-04 02:18:31 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/aLQF6JoRjO/ea_profile.json
* 2023-02-04 02:18:31 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-04 02:18:33 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-06 02:18:22 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-06 02:18:22 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-06 02:18:22 (3898) [[32mINFO[0m] 
* 2023-02-06 02:18:22 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-06 02:18:22 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-06 02:18:22 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-06 02:18:22 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-06 02:18:22 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-02-06 02:18:22 (3929) [[32mINFO[0m] 
* 2023-02-06 02:18:22 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-06 02:18:22 (3898) [[32mINFO[0m] 
* 2023-02-06 02:20:47 (3912) [[32mINFO[0m] http://mirrors.nipa.cloud/epel/7/x86_64/repodata/d22438a5bba5461266f439a960e3835cbf2448ff694eb986c80310c9333552c8-primary.sqlite.bz2: [Errno 12] Timeout on http://mirrors.nipa.cloud/epel/7/x86_64/repodata/d22438a5bba5461266f439a960e3835cbf2448ff694eb986c80310c9333552c8-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-02-06 02:20:47 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-06 02:21:06 (3929) [[32mINFO[0m] 
* 2023-02-06 02:21:06 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-06 02:21:06 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-06 02:21:06 (3898) [[32mINFO[0m] 
* 2023-02-06 02:21:06 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-06 02:21:08 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-06 02:21:08 (3929) [[32mINFO[0m] 
* 2023-02-06 02:21:08 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-06 02:21:08 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rhO5n87a6t/ea_profile.json
* 2023-02-06 02:21:09 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/rhO5n87a6t/ea_profile.json
* 2023-02-06 02:21:09 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-06 02:21:11 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-08 02:18:52 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-08 02:18:53 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-08 02:18:53 (3898) [[32mINFO[0m] 
* 2023-02-08 02:18:53 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-08 02:18:53 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-08 02:18:53 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-08 02:18:55 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-08 02:18:55 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-02-08 02:18:55 (3929) [[32mINFO[0m] 
* 2023-02-08 02:18:55 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-08 02:18:55 (3898) [[32mINFO[0m] 
* 2023-02-08 02:19:18 (3912) [[32mINFO[0m] http://184.94.196.97/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/b581bf8bf1ad82e71ed12073db679f5253256410bf48b3ca193a2eab1504f83b-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
* 2023-02-08 02:19:18 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-08 02:20:12 (3912) [[32mINFO[0m] 
* 2023-02-08 02:20:12 (3912) [[32mINFO[0m] MariaDB-client.x86_64              10.3.38-1.el7.centos               MariaDB103
* 2023-02-08 02:20:12 (3912) [[32mINFO[0m] MariaDB-common.x86_64              10.3.38-1.el7.centos               MariaDB103
* 2023-02-08 02:20:12 (3912) [[32mINFO[0m] MariaDB-compat.x86_64              10.3.38-1.el7.centos               MariaDB103
* 2023-02-08 02:20:12 (3912) [[32mINFO[0m] MariaDB-devel.x86_64               10.3.38-1.el7.centos               MariaDB103
* 2023-02-08 02:20:12 (3912) [[32mINFO[0m] MariaDB-server.x86_64              10.3.38-1.el7.centos               MariaDB103
* 2023-02-08 02:20:12 (3912) [[32mINFO[0m] MariaDB-shared.x86_64              10.3.38-1.el7.centos               MariaDB103
* 2023-02-08 02:20:13 (3929) [[32mINFO[0m] 
* 2023-02-08 02:20:13 (3393) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-08 02:20:13 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-08 02:20:13 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-08 02:20:13 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bmt8dkkkON/ea_profile.json
* 2023-02-08 02:20:14 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/bmt8dkkkON/ea_profile.json
* 2023-02-08 02:20:14 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-08 02:20:15 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-09 02:13:44 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-09 02:13:44 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-09 02:13:44 (3898) [[32mINFO[0m] 
* 2023-02-09 02:13:44 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-09 02:13:44 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-09 02:13:44 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-09 02:13:45 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-09 02:13:45 (3912) [[32mINFO[0m] Other repos take up 396 k of disk space (use --verbose for details)
* 2023-02-09 02:13:45 (3929) [[32mINFO[0m] 
* 2023-02-09 02:13:45 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-09 02:13:45 (3898) [[32mINFO[0m] 
* 2023-02-09 02:14:15 (3912) [[32mINFO[0m] 
* 2023-02-09 02:14:15 (3912) [[32mINFO[0m] MariaDB-client.x86_64              10.3.38-1.el7.centos               MariaDB103
* 2023-02-09 02:14:15 (3912) [[32mINFO[0m] MariaDB-common.x86_64              10.3.38-1.el7.centos               MariaDB103
* 2023-02-09 02:14:15 (3912) [[32mINFO[0m] MariaDB-compat.x86_64              10.3.38-1.el7.centos               MariaDB103
* 2023-02-09 02:14:15 (3912) [[32mINFO[0m] MariaDB-devel.x86_64               10.3.38-1.el7.centos               MariaDB103
* 2023-02-09 02:14:15 (3912) [[32mINFO[0m] MariaDB-server.x86_64              10.3.38-1.el7.centos               MariaDB103
* 2023-02-09 02:14:15 (3912) [[32mINFO[0m] MariaDB-shared.x86_64              10.3.38-1.el7.centos               MariaDB103
* 2023-02-09 02:14:15 (3929) [[32mINFO[0m] 
* 2023-02-09 02:14:15 (3393) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-09 02:14:15 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-09 02:14:15 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-09 02:14:16 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OHVUFw8S8m/ea_profile.json
* 2023-02-09 02:14:18 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/OHVUFw8S8m/ea_profile.json
* 2023-02-09 02:14:18 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-09 02:14:19 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-10 02:14:35 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-10 02:14:35 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-10 02:14:35 (3898) [[32mINFO[0m] 
* 2023-02-10 02:14:35 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-10 02:14:36 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-10 02:14:36 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-10 02:14:36 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-10 02:14:36 (3912) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-10 02:14:36 (3929) [[32mINFO[0m] 
* 2023-02-10 02:14:36 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-10 02:14:36 (3898) [[32mINFO[0m] 
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] 
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] MariaDB-client.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] MariaDB-common.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] MariaDB-compat.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] MariaDB-devel.x86_64                      10.3.38-1.el7.centos        MariaDB103
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] MariaDB-server.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] MariaDB-shared.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24.x86_64                        2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-config.noarch                 1.0-190.193.3.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-config-runtime.noarch         1.0-190.193.3.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-mod_bwlimited.x86_64          1.4-47.54.9.cpanel          EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-mod_cgid.x86_64               2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-mod_deflate.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-mod_expires.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-mod_headers.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-mod_http2.x86_64              2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-mod_mpm_worker.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-mod_proxy.x86_64              2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_fcgi.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_http.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_wstunnel.x86_64     2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-mod_security2.x86_64          2.9.6-2.2.10.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-mod_ssl.x86_64                2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-mod_suexec.x86_64             2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-mod_suphp.x86_64              0.7.2-32.36.10.cpanel       EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-mod_unique_id.x86_64          2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apache24-tools.x86_64                  2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apr.x86_64                             1.7.2-1.1.2.cpanel          EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-apr-util.x86_64                        1.6.3-1.1.1.cpanel          EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-libcurl.x86_64                         7.87.0-2.2.1.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-libnghttp2.x86_64                      1.51.0-2.2.1.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-libxml2.x86_64                         2.10.3-1.1.1.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-modsec-sdbm-util.x86_64                0.02-3.5.2.cpanel           EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-nghttp2.x86_64                         1.51.0-2.2.1.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-openssl11.x86_64                       1.1.1t-1.1.1.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-openssl11-devel.x86_64                 1.1.1t-1.1.1.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-bcmath.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-bz2.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-calendar.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-cli.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-common.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-curl.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-dba.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-devel.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-enchant.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-exif.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-fileinfo.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-fpm.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-ftp.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-gd.x86_64                    5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-gettext.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-gmp.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-iconv.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-imap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-intl.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-ldap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-litespeed.x86_64             5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-mbstring.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-mcrypt.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-mysqlnd.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-odbc.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-pdo.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-pgsql.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-posix.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-process.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-pspell.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-snmp.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-soap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-sockets.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-tidy.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-xml.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-xmlrpc.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-zendguard.x86_64             3.3-9.9.7.cpanel            EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php54-php-zip.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-bcmath.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-bz2.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-calendar.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-cli.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-common.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-curl.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-dba.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-devel.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-enchant.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-exif.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-fileinfo.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-fpm.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-ftp.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-gd.x86_64                    5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-gettext.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-gmp.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-iconv.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-imap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-intl.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-ldap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-litespeed.x86_64             5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-mbstring.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-mcrypt.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-mysqlnd.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-odbc.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-opcache.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-pdo.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-pgsql.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-posix.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-process.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-pspell.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-snmp.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-soap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-sockets.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-sourceguardian.x86_64        14.0.0-1.2.2.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-tidy.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-xml.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-xmlrpc.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php56-php-zip.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-bcmath.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-bz2.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-calendar.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-cli.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-common.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-curl.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-dba.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-devel.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-enchant.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-exif.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-fileinfo.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-fpm.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-ftp.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-gd.x86_64                    7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-gettext.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-gmp.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-iconv.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-imap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-intl.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-ldap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-litespeed.x86_64             7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-mbstring.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-mysqlnd.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-odbc.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-opcache.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-pdo.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-pgsql.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-posix.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-process.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-pspell.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-snmp.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-soap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-sockets.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-tidy.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-xml.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-xmlrpc.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php72-php-zip.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-pear.noarch                      1.10.12-6.15.10.cpanel      EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-bcmath.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-bz2.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-calendar.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-cli.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-common.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-curl.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-dba.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-devel.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-enchant.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-exif.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-fileinfo.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-fpm.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-ftp.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-gd.x86_64                    7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-gettext.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-gmp.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-iconv.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-imap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-intl.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-ioncube10.x86_64             10.4.5-5.6.9.cpanel         EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-ldap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-litespeed.x86_64             7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-mbstring.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-mysqlnd.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-odbc.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-opcache.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-pdo.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-pgsql.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-posix.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-process.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-pspell.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-snmp.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-soap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-sockets.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-tidy.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:04 (3912) [[32mINFO[0m] ea-php73-php-xml.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:07 (3912) [[32mINFO[0m] ea-php73-php-xmlrpc.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:07 (3912) [[32mINFO[0m] ea-php73-php-zip.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 02:15:07 (3929) [[32mINFO[0m] 
* 2023-02-10 02:15:07 (3393) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-10 02:15:07 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-10 02:15:07 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-10 02:15:07 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aTXexCfl7Y/ea_profile.json
* 2023-02-10 02:15:08 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/aTXexCfl7Y/ea_profile.json
* 2023-02-10 02:15:08 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-10 02:15:10 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-10 15:51:58 (3552) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-02-10 15:51:58 (3553) [[31mERROR[0m] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/caba779bf0432855528d7c88b14897dc6d1758eac6ec03137af16a0477c6ecf1-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-02-10 15:51:58 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-02-10 15:51:58 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-10 15:51:58 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-10 15:51:58 (3898) [[32mINFO[0m] 
* 2023-02-10 15:51:59 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-10 15:51:59 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-10 15:51:59 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-10 15:51:59 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-10 15:51:59 (3912) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-10 15:51:59 (3929) [[32mINFO[0m] 
* 2023-02-10 15:51:59 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-10 15:51:59 (3898) [[32mINFO[0m] 
* 2023-02-10 15:52:16 (3912) [[32mINFO[0m] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/dfd0328b896af73be35509c6fd832490a2c8e2aab19837670ee8ba66498d7fd4-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-02-10 15:52:16 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-10 15:52:16 (3912) [[32mINFO[0m] To address this issue please refer to the below wiki article 
* 2023-02-10 15:52:16 (3912) [[32mINFO[0m] 
* 2023-02-10 15:52:16 (3912) [[32mINFO[0m] https://wiki.centos.org/yum-errors
* 2023-02-10 15:52:16 (3912) [[32mINFO[0m] 
* 2023-02-10 15:52:16 (3912) [[32mINFO[0m] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2023-02-10 15:52:16 (3912) [[32mINFO[0m] 
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] 
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] MariaDB-client.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] MariaDB-common.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] MariaDB-compat.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] MariaDB-devel.x86_64                      10.3.38-1.el7.centos        MariaDB103
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] MariaDB-server.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] MariaDB-shared.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24.x86_64                        2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-config.noarch                 1.0-190.193.3.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-config-runtime.noarch         1.0-190.193.3.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-mod_bwlimited.x86_64          1.4-47.54.9.cpanel          EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-mod_cgid.x86_64               2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-mod_deflate.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-mod_expires.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-mod_headers.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-mod_http2.x86_64              2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-mod_mpm_worker.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-mod_proxy.x86_64              2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_fcgi.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_http.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_wstunnel.x86_64     2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-mod_security2.x86_64          2.9.6-2.2.10.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-mod_ssl.x86_64                2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-mod_suexec.x86_64             2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-mod_suphp.x86_64              0.7.2-32.36.10.cpanel       EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-mod_unique_id.x86_64          2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apache24-tools.x86_64                  2.4.55-2.2.2.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apr.x86_64                             1.7.2-1.1.2.cpanel          EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-apr-util.x86_64                        1.6.3-1.1.1.cpanel          EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-libcurl.x86_64                         7.87.0-2.2.1.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-libnghttp2.x86_64                      1.51.0-2.2.1.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-libxml2.x86_64                         2.10.3-1.1.1.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-modsec-sdbm-util.x86_64                0.02-3.5.2.cpanel           EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-nghttp2.x86_64                         1.51.0-2.2.1.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-openssl11.x86_64                       1.1.1t-1.1.1.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-openssl11-devel.x86_64                 1.1.1t-1.1.1.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-bcmath.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-bz2.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-calendar.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-cli.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-common.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-curl.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-dba.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-devel.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-enchant.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-exif.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-fileinfo.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-fpm.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-ftp.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-gd.x86_64                    5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-gettext.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-gmp.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-iconv.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-imap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-intl.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-ldap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-litespeed.x86_64             5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-mbstring.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-mcrypt.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-mysqlnd.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-odbc.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-pdo.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-pgsql.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-posix.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-process.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-pspell.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-snmp.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-soap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-sockets.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-tidy.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-xml.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-xmlrpc.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-zendguard.x86_64             3.3-9.9.7.cpanel            EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php54-php-zip.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-bcmath.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-bz2.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-calendar.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-cli.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-common.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-curl.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-dba.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-devel.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-enchant.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-exif.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-fileinfo.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-fpm.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-ftp.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-gd.x86_64                    5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-gettext.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-gmp.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-iconv.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-imap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-intl.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-ldap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-litespeed.x86_64             5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-mbstring.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-mcrypt.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-mysqlnd.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-odbc.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-opcache.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-pdo.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-pgsql.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-posix.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-process.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-pspell.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-snmp.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-soap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-sockets.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-sourceguardian.x86_64        14.0.0-1.2.2.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-tidy.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-xml.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-xmlrpc.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php56-php-zip.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-bcmath.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-bz2.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-calendar.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-cli.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-common.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-curl.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-dba.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-devel.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-enchant.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-exif.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-fileinfo.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-fpm.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-ftp.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-gd.x86_64                    7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-gettext.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-gmp.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-iconv.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-imap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-intl.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-ldap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-litespeed.x86_64             7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-mbstring.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-mysqlnd.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-odbc.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-opcache.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-pdo.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-pgsql.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-posix.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-process.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-pspell.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-snmp.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-soap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-sockets.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-tidy.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-xml.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-xmlrpc.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php72-php-zip.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-pear.noarch                      1.10.12-6.15.10.cpanel      EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-bcmath.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-bz2.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-calendar.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-cli.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-common.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-curl.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-dba.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-devel.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-enchant.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-exif.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-fileinfo.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-fpm.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-ftp.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-gd.x86_64                    7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-gettext.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-gmp.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-iconv.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-imap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-intl.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-ioncube10.x86_64             10.4.5-5.6.9.cpanel         EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-ldap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-litespeed.x86_64             7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-mbstring.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-mysqlnd.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-odbc.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-opcache.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-pdo.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-pgsql.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-posix.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-process.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-pspell.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-snmp.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-soap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-sockets.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-tidy.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:52 (3912) [[32mINFO[0m] ea-php73-php-xml.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:54 (3912) [[32mINFO[0m] ea-php73-php-xmlrpc.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:54 (3912) [[32mINFO[0m] ea-php73-php-zip.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-10 15:52:54 (3929) [[32mINFO[0m] 
* 2023-02-10 15:52:54 (3393) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-10 15:52:54 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-10 15:52:54 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-10 15:52:54 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DTIeHWw_kk/ea_profile.json
* 2023-02-10 15:52:56 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/DTIeHWw_kk/ea_profile.json
* 2023-02-10 15:52:56 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-10 15:52:57 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-11 02:15:39 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-11 02:15:39 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-11 02:15:39 (3898) [[32mINFO[0m] 
* 2023-02-11 02:15:40 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-11 02:15:40 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-11 02:15:40 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-11 02:15:40 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-11 02:15:40 (3912) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-11 02:15:40 (3929) [[32mINFO[0m] 
* 2023-02-11 02:15:40 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-11 02:15:40 (3898) [[32mINFO[0m] 
* 2023-02-11 02:15:56 (3912) [[32mINFO[0m] https://hkg.mirror.rackspace.com/epel/7/x86_64/repodata/45408ec1d6e2881c46c9ae615352e36ef1222d467a21ed6228afcb970865e45e-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-02-11 02:15:56 (3912) [[32mINFO[0m] Trying other mirror.
* 2023-02-11 02:15:56 (3912) [[32mINFO[0m] To address this issue please refer to the below wiki article 
* 2023-02-11 02:15:56 (3912) [[32mINFO[0m] 
* 2023-02-11 02:15:56 (3912) [[32mINFO[0m] https://wiki.centos.org/yum-errors
* 2023-02-11 02:15:56 (3912) [[32mINFO[0m] 
* 2023-02-11 02:15:56 (3912) [[32mINFO[0m] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2023-02-11 02:15:56 (3912) [[32mINFO[0m] 
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] 
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] MariaDB-client.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] MariaDB-common.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] MariaDB-compat.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] MariaDB-devel.x86_64                      10.3.38-1.el7.centos        MariaDB103
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] MariaDB-server.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] MariaDB-shared.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24.x86_64                        2.4.55-2.2.2.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-config.noarch                 1.0-190.193.3.cpanel        EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-config-runtime.noarch         1.0-190.193.3.cpanel        EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-mod_bwlimited.x86_64          1.4-47.54.9.cpanel          EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-mod_cgid.x86_64               2.4.55-2.2.2.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-mod_deflate.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-mod_expires.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-mod_headers.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-mod_http2.x86_64              2.4.55-2.2.2.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-mod_mpm_worker.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-mod_proxy.x86_64              2.4.55-2.2.2.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_fcgi.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_http.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_wstunnel.x86_64     2.4.55-2.2.2.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-mod_security2.x86_64          2.9.6-2.2.10.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-mod_ssl.x86_64                2.4.55-2.2.2.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-mod_suexec.x86_64             2.4.55-2.2.2.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-mod_suphp.x86_64              0.7.2-32.36.10.cpanel       EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-mod_unique_id.x86_64          2.4.55-2.2.2.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apache24-tools.x86_64                  2.4.55-2.2.2.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apr.x86_64                             1.7.2-1.1.2.cpanel          EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-apr-util.x86_64                        1.6.3-1.1.1.cpanel          EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-libcurl.x86_64                         7.87.0-2.2.1.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-libnghttp2.x86_64                      1.51.0-2.2.1.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-libxml2.x86_64                         2.10.3-1.1.1.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-modsec-sdbm-util.x86_64                0.02-3.5.2.cpanel           EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-nghttp2.x86_64                         1.51.0-2.2.1.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-openssl11.x86_64                       1.1.1t-1.1.1.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-openssl11-devel.x86_64                 1.1.1t-1.1.1.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-bcmath.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-bz2.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-calendar.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-cli.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-common.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-curl.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-dba.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-devel.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-enchant.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-exif.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-fileinfo.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-fpm.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-ftp.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-gd.x86_64                    5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-gettext.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-gmp.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-iconv.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-imap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-intl.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-ldap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-litespeed.x86_64             5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-mbstring.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-mcrypt.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-mysqlnd.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-odbc.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-pdo.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-pgsql.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-posix.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-process.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-pspell.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-snmp.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-soap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-sockets.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-tidy.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-xml.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-xmlrpc.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-zendguard.x86_64             3.3-9.9.7.cpanel            EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php54-php-zip.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-bcmath.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-bz2.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-calendar.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-cli.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-common.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-curl.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-dba.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-devel.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-enchant.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-exif.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-fileinfo.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-fpm.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-ftp.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-gd.x86_64                    5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-gettext.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-gmp.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-iconv.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-imap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-intl.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-ldap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-litespeed.x86_64             5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-mbstring.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-mcrypt.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-mysqlnd.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-odbc.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-opcache.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-pdo.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-pgsql.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-posix.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-process.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-pspell.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:12 (3912) [[32mINFO[0m] ea-php56-php-snmp.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php56-php-soap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php56-php-sockets.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php56-php-sourceguardian.x86_64        14.0.0-1.2.2.cpanel         EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php56-php-tidy.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php56-php-xml.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php56-php-xmlrpc.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php56-php-zip.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-bcmath.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-bz2.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-calendar.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-cli.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-common.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-curl.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-dba.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-devel.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-enchant.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-exif.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-fileinfo.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-fpm.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-ftp.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-gd.x86_64                    7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-gettext.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-gmp.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-iconv.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-imap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-intl.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-ldap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-litespeed.x86_64             7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-mbstring.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-mysqlnd.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-odbc.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-opcache.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-pdo.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-pgsql.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-posix.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-process.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-pspell.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-snmp.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-soap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-sockets.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-tidy.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-xml.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-xmlrpc.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php72-php-zip.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-pear.noarch                      1.10.12-6.15.10.cpanel      EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-bcmath.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-bz2.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-calendar.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-cli.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-common.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-curl.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-dba.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-devel.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-enchant.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-exif.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-fileinfo.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-fpm.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-ftp.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-gd.x86_64                    7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-gettext.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-gmp.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-iconv.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-imap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-intl.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-ioncube10.x86_64             10.4.5-5.6.9.cpanel         EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-ldap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-litespeed.x86_64             7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-mbstring.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-mysqlnd.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-odbc.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-opcache.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-pdo.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-pgsql.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-posix.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-process.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-pspell.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-snmp.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-soap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-sockets.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-tidy.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:13 (3912) [[32mINFO[0m] ea-php73-php-xml.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:15 (3912) [[32mINFO[0m] ea-php73-php-xmlrpc.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:15 (3912) [[32mINFO[0m] ea-php73-php-zip.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-11 02:16:15 (3929) [[32mINFO[0m] 
* 2023-02-11 02:16:15 (3393) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-11 02:16:15 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-11 02:16:15 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-11 02:16:15 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fV55XnwRtm/ea_profile.json
* 2023-02-11 02:16:17 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/fV55XnwRtm/ea_profile.json
* 2023-02-11 02:16:17 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-11 02:16:18 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-12 02:14:46 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-12 02:14:46 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-12 02:14:46 (3898) [[32mINFO[0m] 
* 2023-02-12 02:14:47 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-12 02:14:47 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-12 02:14:47 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-12 02:14:47 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-12 02:14:47 (3912) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-12 02:14:47 (3929) [[32mINFO[0m] 
* 2023-02-12 02:14:47 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-12 02:14:47 (3898) [[32mINFO[0m] 
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] 
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] MariaDB-client.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] MariaDB-common.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] MariaDB-compat.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] MariaDB-devel.x86_64                      10.3.38-1.el7.centos        MariaDB103
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] MariaDB-server.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] MariaDB-shared.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24.x86_64                        2.4.55-2.2.2.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-config.noarch                 1.0-190.193.3.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-config-runtime.noarch         1.0-190.193.3.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-mod_bwlimited.x86_64          1.4-47.54.9.cpanel          EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-mod_cgid.x86_64               2.4.55-2.2.2.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-mod_deflate.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-mod_expires.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-mod_headers.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-mod_http2.x86_64              2.4.55-2.2.2.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-mod_mpm_worker.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-mod_proxy.x86_64              2.4.55-2.2.2.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_fcgi.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_http.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_wstunnel.x86_64     2.4.55-2.2.2.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-mod_security2.x86_64          2.9.6-2.2.10.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-mod_ssl.x86_64                2.4.55-2.2.2.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-mod_suexec.x86_64             2.4.55-2.2.2.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-mod_suphp.x86_64              0.7.2-32.36.10.cpanel       EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-mod_unique_id.x86_64          2.4.55-2.2.2.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apache24-tools.x86_64                  2.4.55-2.2.2.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apr.x86_64                             1.7.2-1.1.2.cpanel          EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-apr-util.x86_64                        1.6.3-1.1.1.cpanel          EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-libcurl.x86_64                         7.87.0-2.2.1.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-libnghttp2.x86_64                      1.51.0-2.2.1.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-libxml2.x86_64                         2.10.3-1.1.1.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-modsec-sdbm-util.x86_64                0.02-3.5.2.cpanel           EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-nghttp2.x86_64                         1.51.0-2.2.1.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-openssl11.x86_64                       1.1.1t-1.1.1.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-openssl11-devel.x86_64                 1.1.1t-1.1.1.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-bcmath.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-bz2.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-calendar.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-cli.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-common.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-curl.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-dba.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-devel.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-enchant.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-exif.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-fileinfo.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-fpm.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-ftp.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-gd.x86_64                    5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-gettext.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-gmp.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-iconv.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-imap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-intl.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-ldap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-litespeed.x86_64             5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-mbstring.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-mcrypt.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-mysqlnd.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-odbc.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-pdo.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-pgsql.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-posix.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-process.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-pspell.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-snmp.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-soap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-sockets.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-tidy.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-xml.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-xmlrpc.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-zendguard.x86_64             3.3-9.9.7.cpanel            EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php54-php-zip.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-bcmath.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-bz2.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-calendar.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-cli.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-common.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-curl.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-dba.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-devel.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-enchant.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-exif.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-fileinfo.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-fpm.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-ftp.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-gd.x86_64                    5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-gettext.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-gmp.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-iconv.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-imap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-intl.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-ldap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-litespeed.x86_64             5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-mbstring.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-mcrypt.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-mysqlnd.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-odbc.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-opcache.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-pdo.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-pgsql.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-posix.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-process.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-pspell.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-snmp.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-soap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-sockets.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-sourceguardian.x86_64        14.0.0-1.2.2.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-tidy.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-xml.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-xmlrpc.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php56-php-zip.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-bcmath.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-bz2.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-calendar.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-cli.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-common.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-curl.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-dba.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-devel.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-enchant.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-exif.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-fileinfo.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-fpm.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-ftp.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-gd.x86_64                    7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-gettext.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-gmp.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-iconv.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-imap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-intl.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-ldap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-litespeed.x86_64             7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-mbstring.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-mysqlnd.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-odbc.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-opcache.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-pdo.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-pgsql.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-posix.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-process.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-pspell.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-snmp.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-soap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-sockets.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-tidy.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-xml.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-xmlrpc.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php72-php-zip.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-pear.noarch                      1.10.12-6.15.10.cpanel      EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-bcmath.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-bz2.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-calendar.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-cli.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-common.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-curl.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-dba.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-devel.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-enchant.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-exif.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-fileinfo.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-fpm.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-ftp.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-gd.x86_64                    7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-gettext.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-gmp.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-iconv.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-imap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-intl.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-ioncube10.x86_64             10.4.5-5.6.9.cpanel         EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-ldap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-litespeed.x86_64             7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-mbstring.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-mysqlnd.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-odbc.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-opcache.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-pdo.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-pgsql.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-posix.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-process.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-pspell.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-snmp.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-soap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-sockets.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-tidy.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:17 (3912) [[32mINFO[0m] ea-php73-php-xml.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:19 (3912) [[32mINFO[0m] ea-php73-php-xmlrpc.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:19 (3912) [[32mINFO[0m] ea-php73-php-zip.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-12 02:15:20 (3929) [[32mINFO[0m] 
* 2023-02-12 02:15:20 (3393) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-12 02:15:20 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-12 02:15:20 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-12 02:15:20 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RWfO2cg5k_/ea_profile.json
* 2023-02-12 02:15:21 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/RWfO2cg5k_/ea_profile.json
* 2023-02-12 02:15:21 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-12 02:15:22 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-13 02:15:27 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-13 02:15:27 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-13 02:15:27 (3898) [[32mINFO[0m] 
* 2023-02-13 02:15:28 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-13 02:15:28 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-13 02:15:28 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-13 02:15:29 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-13 02:15:29 (3912) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-13 02:15:29 (3929) [[32mINFO[0m] 
* 2023-02-13 02:15:29 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-13 02:15:29 (3898) [[32mINFO[0m] 
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] 
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] MariaDB-client.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] MariaDB-common.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] MariaDB-compat.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] MariaDB-devel.x86_64                      10.3.38-1.el7.centos        MariaDB103
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] MariaDB-server.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] MariaDB-shared.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24.x86_64                        2.4.55-2.2.2.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-config.noarch                 1.0-190.193.3.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-config-runtime.noarch         1.0-190.193.3.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-mod_bwlimited.x86_64          1.4-47.54.9.cpanel          EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-mod_cgid.x86_64               2.4.55-2.2.2.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-mod_deflate.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-mod_expires.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-mod_headers.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-mod_http2.x86_64              2.4.55-2.2.2.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-mod_mpm_worker.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-mod_proxy.x86_64              2.4.55-2.2.2.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_fcgi.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_http.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_wstunnel.x86_64     2.4.55-2.2.2.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-mod_security2.x86_64          2.9.6-2.2.10.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-mod_ssl.x86_64                2.4.55-2.2.2.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-mod_suexec.x86_64             2.4.55-2.2.2.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-mod_suphp.x86_64              0.7.2-32.36.10.cpanel       EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-mod_unique_id.x86_64          2.4.55-2.2.2.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apache24-tools.x86_64                  2.4.55-2.2.2.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apr.x86_64                             1.7.2-1.1.2.cpanel          EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-apr-util.x86_64                        1.6.3-1.1.1.cpanel          EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-libcurl.x86_64                         7.87.0-2.2.1.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-libnghttp2.x86_64                      1.51.0-2.2.1.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-libxml2.x86_64                         2.10.3-1.1.1.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-modsec-sdbm-util.x86_64                0.02-3.5.2.cpanel           EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-nghttp2.x86_64                         1.51.0-2.2.1.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-openssl11.x86_64                       1.1.1t-1.1.1.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-openssl11-devel.x86_64                 1.1.1t-1.1.1.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-bcmath.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-bz2.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-calendar.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-cli.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-common.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-curl.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-dba.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-devel.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-enchant.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-exif.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-fileinfo.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-fpm.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-ftp.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-gd.x86_64                    5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-gettext.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-gmp.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-iconv.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-imap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-intl.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-ldap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-litespeed.x86_64             5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-mbstring.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-mcrypt.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-mysqlnd.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-odbc.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-pdo.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-pgsql.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-posix.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-process.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-pspell.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-snmp.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-soap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-sockets.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-tidy.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-xml.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-xmlrpc.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-zendguard.x86_64             3.3-9.9.7.cpanel            EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php54-php-zip.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-bcmath.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-bz2.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-calendar.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-cli.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-common.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-curl.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-dba.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-devel.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-enchant.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-exif.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-fileinfo.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-fpm.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-ftp.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-gd.x86_64                    5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-gettext.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-gmp.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-iconv.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-imap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-intl.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-ldap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-litespeed.x86_64             5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-mbstring.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-mcrypt.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-mysqlnd.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-odbc.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-opcache.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-pdo.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-pgsql.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-posix.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-process.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-pspell.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-snmp.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-soap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-sockets.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-sourceguardian.x86_64        14.0.0-1.2.2.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-tidy.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-xml.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-xmlrpc.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php56-php-zip.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-bcmath.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-bz2.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-calendar.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-cli.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-common.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-curl.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-dba.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-devel.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-enchant.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-exif.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-fileinfo.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-fpm.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-ftp.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-gd.x86_64                    7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-gettext.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-gmp.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-iconv.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-imap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-intl.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-ldap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-litespeed.x86_64             7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-mbstring.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-mysqlnd.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-odbc.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-opcache.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-pdo.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-pgsql.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-posix.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-process.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-pspell.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-snmp.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-soap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-sockets.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-tidy.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-xml.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-xmlrpc.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php72-php-zip.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-pear.noarch                      1.10.12-6.15.10.cpanel      EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-bcmath.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-bz2.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-calendar.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-cli.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-common.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-curl.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-dba.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-devel.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-enchant.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-exif.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-fileinfo.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-fpm.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-ftp.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-gd.x86_64                    7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-gettext.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-gmp.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-iconv.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-imap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-intl.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-ioncube10.x86_64             10.4.5-5.6.9.cpanel         EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-ldap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-litespeed.x86_64             7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-mbstring.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-mysqlnd.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-odbc.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-opcache.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-pdo.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-pgsql.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-posix.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-process.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-pspell.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-snmp.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-soap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-sockets.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-tidy.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:18 (3912) [[32mINFO[0m] ea-php73-php-xml.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:21 (3912) [[32mINFO[0m] ea-php73-php-xmlrpc.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:21 (3912) [[32mINFO[0m] ea-php73-php-zip.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-13 02:16:22 (3929) [[32mINFO[0m] 
* 2023-02-13 02:16:22 (3393) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-13 02:16:22 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-13 02:16:22 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-13 02:16:22 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/j41bZ1jVGZ/ea_profile.json
* 2023-02-13 02:16:56 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/j41bZ1jVGZ/ea_profile.json
* 2023-02-13 02:16:56 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-13 02:17:00 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-14 02:14:07 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-14 02:14:07 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-14 02:14:07 (3898) [[32mINFO[0m] 
* 2023-02-14 02:14:08 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-14 02:14:08 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-14 02:14:08 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-14 02:14:08 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-14 02:14:08 (3912) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-14 02:14:08 (3929) [[32mINFO[0m] 
* 2023-02-14 02:14:08 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-14 02:14:08 (3898) [[32mINFO[0m] 
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] 
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] MariaDB-client.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] MariaDB-common.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] MariaDB-compat.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] MariaDB-devel.x86_64                      10.3.38-1.el7.centos        MariaDB103
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] MariaDB-server.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] MariaDB-shared.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24.x86_64                        2.4.55-2.2.2.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-config.noarch                 1.0-190.193.3.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-config-runtime.noarch         1.0-190.193.3.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-mod_bwlimited.x86_64          1.4-47.54.9.cpanel          EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-mod_cgid.x86_64               2.4.55-2.2.2.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-mod_deflate.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-mod_expires.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-mod_headers.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-mod_http2.x86_64              2.4.55-2.2.2.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-mod_mpm_worker.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-mod_proxy.x86_64              2.4.55-2.2.2.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_fcgi.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_http.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_wstunnel.x86_64     2.4.55-2.2.2.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-mod_security2.x86_64          2.9.6-2.2.10.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-mod_ssl.x86_64                2.4.55-2.2.2.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-mod_suexec.x86_64             2.4.55-2.2.2.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-mod_suphp.x86_64              0.7.2-32.36.10.cpanel       EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-mod_unique_id.x86_64          2.4.55-2.2.2.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apache24-tools.x86_64                  2.4.55-2.2.2.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apr.x86_64                             1.7.2-1.1.2.cpanel          EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-apr-util.x86_64                        1.6.3-1.1.1.cpanel          EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-libcurl.x86_64                         7.87.0-2.2.1.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-libnghttp2.x86_64                      1.51.0-2.2.1.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-libxml2.x86_64                         2.10.3-1.1.1.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-modsec-sdbm-util.x86_64                0.02-3.5.2.cpanel           EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-nghttp2.x86_64                         1.51.0-2.2.1.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-openssl11.x86_64                       1.1.1t-1.1.1.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-openssl11-devel.x86_64                 1.1.1t-1.1.1.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-bcmath.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-bz2.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-calendar.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-cli.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-common.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-curl.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-dba.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-devel.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-enchant.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-exif.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-fileinfo.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-fpm.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-ftp.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-gd.x86_64                    5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-gettext.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-gmp.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-iconv.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-imap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-intl.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-ldap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-litespeed.x86_64             5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-mbstring.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-mcrypt.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-mysqlnd.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-odbc.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-pdo.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-pgsql.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-posix.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-process.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-pspell.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-snmp.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-soap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-sockets.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-tidy.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-xml.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-xmlrpc.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-zendguard.x86_64             3.3-9.9.7.cpanel            EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php54-php-zip.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-bcmath.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-bz2.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-calendar.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-cli.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-common.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-curl.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-dba.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-devel.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-enchant.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-exif.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-fileinfo.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-fpm.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-ftp.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-gd.x86_64                    5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-gettext.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-gmp.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-iconv.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-imap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-intl.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-ldap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-litespeed.x86_64             5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-mbstring.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-mcrypt.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-mysqlnd.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-odbc.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-opcache.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-pdo.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-pgsql.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-posix.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-process.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-pspell.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-snmp.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-soap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-sockets.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-sourceguardian.x86_64        14.0.0-1.2.2.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-tidy.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-xml.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-xmlrpc.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php56-php-zip.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-bcmath.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-bz2.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-calendar.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-cli.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-common.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-curl.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-dba.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-devel.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-enchant.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-exif.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-fileinfo.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-fpm.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-ftp.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-gd.x86_64                    7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-gettext.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-gmp.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-iconv.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-imap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-intl.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-ldap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-litespeed.x86_64             7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-mbstring.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-mysqlnd.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-odbc.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-opcache.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-pdo.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-pgsql.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-posix.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-process.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-pspell.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-snmp.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-soap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-sockets.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-tidy.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-xml.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-xmlrpc.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php72-php-zip.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-pear.noarch                      1.10.12-6.15.10.cpanel      EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-bcmath.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-bz2.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-calendar.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-cli.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-common.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-curl.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-dba.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-devel.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-enchant.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-exif.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-fileinfo.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-fpm.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-ftp.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-gd.x86_64                    7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-gettext.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-gmp.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-iconv.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-imap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-intl.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-ioncube10.x86_64             10.4.5-5.6.9.cpanel         EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-ldap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-litespeed.x86_64             7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-mbstring.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-mysqlnd.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-odbc.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-opcache.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-pdo.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-pgsql.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-posix.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-process.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-pspell.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-snmp.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-soap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-sockets.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-tidy.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:39 (3912) [[32mINFO[0m] ea-php73-php-xml.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:42 (3912) [[32mINFO[0m] ea-php73-php-xmlrpc.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:42 (3912) [[32mINFO[0m] ea-php73-php-zip.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-14 02:14:42 (3929) [[32mINFO[0m] 
* 2023-02-14 02:14:42 (3393) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-14 02:14:42 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-14 02:14:42 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-14 02:14:42 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SO8FaWjx3u/ea_profile.json
* 2023-02-14 02:14:43 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/SO8FaWjx3u/ea_profile.json
* 2023-02-14 02:14:43 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-14 02:14:45 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-15 02:16:52 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-15 02:16:52 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-15 02:16:52 (3898) [[32mINFO[0m] 
* 2023-02-15 02:16:53 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-15 02:16:53 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-15 02:16:53 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-15 02:16:53 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-15 02:16:53 (3912) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-15 02:16:53 (3929) [[32mINFO[0m] 
* 2023-02-15 02:16:53 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-15 02:16:53 (3898) [[32mINFO[0m] 
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] 
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] MariaDB-client.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] MariaDB-common.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] MariaDB-compat.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] MariaDB-devel.x86_64                      10.3.38-1.el7.centos        MariaDB103
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] MariaDB-server.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] MariaDB-shared.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24.x86_64                        2.4.55-2.2.2.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-config.noarch                 1.0-190.193.3.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-config-runtime.noarch         1.0-190.193.3.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-mod_bwlimited.x86_64          1.4-47.54.9.cpanel          EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-mod_cgid.x86_64               2.4.55-2.2.2.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-mod_deflate.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-mod_expires.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-mod_headers.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-mod_http2.x86_64              2.4.55-2.2.2.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-mod_mpm_worker.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-mod_proxy.x86_64              2.4.55-2.2.2.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_fcgi.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_http.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_wstunnel.x86_64     2.4.55-2.2.2.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-mod_security2.x86_64          2.9.6-2.2.10.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-mod_ssl.x86_64                2.4.55-2.2.2.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-mod_suexec.x86_64             2.4.55-2.2.2.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-mod_suphp.x86_64              0.7.2-32.36.10.cpanel       EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-mod_unique_id.x86_64          2.4.55-2.2.2.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apache24-tools.x86_64                  2.4.55-2.2.2.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apr.x86_64                             1.7.2-1.1.2.cpanel          EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-apr-util.x86_64                        1.6.3-1.1.1.cpanel          EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-libcurl.x86_64                         7.87.0-2.2.1.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-libnghttp2.x86_64                      1.51.0-2.2.1.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-libxml2.x86_64                         2.10.3-1.1.1.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-modsec-sdbm-util.x86_64                0.02-3.5.2.cpanel           EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-nghttp2.x86_64                         1.51.0-2.2.1.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-openssl11.x86_64                       1.1.1t-1.1.1.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-openssl11-devel.x86_64                 1.1.1t-1.1.1.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-bcmath.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-bz2.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-calendar.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-cli.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-common.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-curl.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-dba.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-devel.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-enchant.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-exif.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-fileinfo.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-fpm.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-ftp.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-gd.x86_64                    5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-gettext.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-gmp.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-iconv.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-imap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-intl.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-ldap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-litespeed.x86_64             5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-mbstring.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-mcrypt.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-mysqlnd.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-odbc.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-pdo.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-pgsql.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-posix.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-process.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-pspell.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-snmp.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-soap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-sockets.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-tidy.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-xml.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-xmlrpc.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-zendguard.x86_64             3.3-9.9.7.cpanel            EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php54-php-zip.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-bcmath.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-bz2.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-calendar.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-cli.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-common.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-curl.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-dba.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-devel.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-enchant.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-exif.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-fileinfo.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-fpm.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-ftp.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-gd.x86_64                    5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-gettext.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-gmp.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-iconv.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-imap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-intl.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-ldap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-litespeed.x86_64             5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-mbstring.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-mcrypt.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-mysqlnd.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-odbc.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-opcache.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-pdo.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-pgsql.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-posix.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-process.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-pspell.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-snmp.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-soap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-sockets.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-sourceguardian.x86_64        14.0.0-1.2.2.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-tidy.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-xml.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-xmlrpc.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php56-php-zip.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-bcmath.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-bz2.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-calendar.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-cli.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-common.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-curl.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-dba.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-devel.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-enchant.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-exif.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-fileinfo.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-fpm.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-ftp.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-gd.x86_64                    7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-gettext.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-gmp.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-iconv.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-imap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-intl.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-ldap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-litespeed.x86_64             7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-mbstring.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-mysqlnd.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-odbc.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-opcache.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-pdo.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-pgsql.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-posix.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-process.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-pspell.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-snmp.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-soap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-sockets.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-tidy.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-xml.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-xmlrpc.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php72-php-zip.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-pear.noarch                      1.10.12-6.15.10.cpanel      EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-bcmath.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-bz2.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-calendar.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-cli.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-common.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-curl.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-dba.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-devel.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-enchant.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-exif.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-fileinfo.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-fpm.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-ftp.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-gd.x86_64                    7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-gettext.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-gmp.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-iconv.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-imap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-intl.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-ioncube10.x86_64             10.4.5-5.6.9.cpanel         EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-ldap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-litespeed.x86_64             7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-mbstring.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-mysqlnd.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-odbc.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-opcache.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-pdo.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-pgsql.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-posix.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-process.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-pspell.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-snmp.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-soap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-sockets.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-tidy.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:22 (3912) [[32mINFO[0m] ea-php73-php-xml.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:25 (3912) [[32mINFO[0m] ea-php73-php-xmlrpc.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:25 (3912) [[32mINFO[0m] ea-php73-php-zip.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-15 02:17:25 (3929) [[32mINFO[0m] 
* 2023-02-15 02:17:25 (3393) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-15 02:17:25 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-15 02:17:25 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-15 02:17:25 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mcq2yO1KZk/ea_profile.json
* 2023-02-15 02:17:27 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/mcq2yO1KZk/ea_profile.json
* 2023-02-15 02:17:27 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-15 02:17:27 (2727) [[33mWARN[0m] *** 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:17:28 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-16 02:19:48 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-16 02:19:48 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-16 02:19:48 (3898) [[32mINFO[0m] 
* 2023-02-16 02:19:49 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-16 02:19:49 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-16 02:19:49 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-16 02:19:49 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-16 02:19:49 (3912) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-16 02:19:49 (3929) [[32mINFO[0m] 
* 2023-02-16 02:19:49 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-16 02:19:49 (3898) [[32mINFO[0m] 
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] 
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] MariaDB-client.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] MariaDB-common.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] MariaDB-compat.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] MariaDB-devel.x86_64                      10.3.38-1.el7.centos        MariaDB103
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] MariaDB-server.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] MariaDB-shared.x86_64                     10.3.38-1.el7.centos        MariaDB103
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24.x86_64                        2.4.55-2.2.2.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-config.noarch                 1.0-190.193.3.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-config-runtime.noarch         1.0-190.193.3.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-mod_bwlimited.x86_64          1.4-47.54.9.cpanel          EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-mod_cgid.x86_64               2.4.55-2.2.2.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-mod_deflate.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-mod_expires.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-mod_headers.x86_64            2.4.55-2.2.2.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-mod_http2.x86_64              2.4.55-2.2.2.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-mod_mpm_worker.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-mod_proxy.x86_64              2.4.55-2.2.2.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_fcgi.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_http.x86_64         2.4.55-2.2.2.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-mod_proxy_wstunnel.x86_64     2.4.55-2.2.2.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-mod_security2.x86_64          2.9.6-2.2.10.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-mod_ssl.x86_64                2.4.55-2.2.2.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-mod_suexec.x86_64             2.4.55-2.2.2.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-mod_suphp.x86_64              0.7.2-32.36.10.cpanel       EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-mod_unique_id.x86_64          2.4.55-2.2.2.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apache24-tools.x86_64                  2.4.55-2.2.2.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apr.x86_64                             1.7.2-1.1.2.cpanel          EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-apr-util.x86_64                        1.6.3-1.1.1.cpanel          EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-libcurl.x86_64                         7.87.0-2.2.1.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-libnghttp2.x86_64                      1.51.0-2.2.1.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-libxml2.x86_64                         2.10.3-1.1.1.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-modsec-sdbm-util.x86_64                0.02-3.5.2.cpanel           EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-nghttp2.x86_64                         1.51.0-2.2.1.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-openssl11.x86_64                       1.1.1t-1.1.1.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-openssl11-devel.x86_64                 1.1.1t-1.1.1.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-bcmath.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-bz2.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-calendar.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-cli.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-common.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-curl.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-dba.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-devel.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-enchant.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-exif.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-fileinfo.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-fpm.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-ftp.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-gd.x86_64                    5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-gettext.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-gmp.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-iconv.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-imap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-intl.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-ldap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-litespeed.x86_64             5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-mbstring.x86_64              5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-mcrypt.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-mysqlnd.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-odbc.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-pdo.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-pgsql.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-posix.x86_64                 5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-process.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-pspell.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-snmp.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-soap.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-sockets.x86_64               5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-tidy.x86_64                  5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-xml.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-xmlrpc.x86_64                5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-zendguard.x86_64             3.3-9.9.7.cpanel            EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php54-php-zip.x86_64                   5.4.45-76.78.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-bcmath.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-bz2.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-calendar.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-cli.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-common.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-curl.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-dba.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-devel.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-enchant.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-exif.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-fileinfo.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-fpm.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-ftp.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-gd.x86_64                    5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-gettext.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-gmp.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-iconv.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-imap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-intl.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-ldap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-litespeed.x86_64             5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-mbstring.x86_64              5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-mcrypt.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-mysqlnd.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-odbc.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-opcache.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-pdo.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-pgsql.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-posix.x86_64                 5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-process.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-pspell.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-snmp.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-soap.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-sockets.x86_64               5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-sourceguardian.x86_64        14.0.0-1.2.2.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-tidy.x86_64                  5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-xml.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-xmlrpc.x86_64                5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php56-php-zip.x86_64                   5.6.40-21.23.30.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-libc-client-devel.x86_64         2007f-23.24.2.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-libc-client-static.x86_64        2007f-23.24.2.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-pear.noarch                      1.10.12-6.15.8.cpanel       EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-bcmath.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-bz2.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-calendar.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-cli.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-common.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-curl.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-dba.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-devel.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-enchant.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-exif.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-fileinfo.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-fpm.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-ftp.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-gd.x86_64                    7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-gettext.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-gmp.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-iconv.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-imap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-intl.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-ioncube10.x86_64             10.4.5-5.6.7.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-ldap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-litespeed.x86_64             7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-mbstring.x86_64              7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-mysqlnd.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-odbc.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-opcache.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-pdo.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-pgsql.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-posix.x86_64                 7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-process.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-pspell.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-snmp.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-soap.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-sockets.x86_64               7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-tidy.x86_64                  7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-xml.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-xmlrpc.x86_64                7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php72-php-zip.x86_64                   7.2.34-7.9.30.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-libc-client.x86_64               2007f-23.24.2.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-pear.noarch                      1.10.12-6.15.10.cpanel      EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-bcmath.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-bz2.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-calendar.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-cli.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-common.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-curl.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-dba.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-devel.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-enchant.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-exif.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-fileinfo.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-fpm.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-ftp.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-gd.x86_64                    7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-gettext.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-gmp.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-iconv.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-imap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-intl.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-ioncube10.x86_64             10.4.5-5.6.9.cpanel         EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-ldap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-litespeed.x86_64             7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-mbstring.x86_64              7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-mysqlnd.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-odbc.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-opcache.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-pdo.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-pgsql.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-posix.x86_64                 7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-process.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-pspell.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-snmp.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-soap.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-sockets.x86_64               7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-tidy.x86_64                  7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:50 (3912) [[32mINFO[0m] ea-php73-php-xml.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:53 (3912) [[32mINFO[0m] ea-php73-php-xmlrpc.x86_64                7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:53 (3912) [[32mINFO[0m] ea-php73-php-zip.x86_64                   7.3.33-5.7.12.cpanel        EA4       
* 2023-02-16 02:20:53 (3929) [[32mINFO[0m] 
* 2023-02-16 02:20:53 (3393) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-16 02:20:53 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-16 02:20:53 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-16 02:20:53 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DOolnrW7Lv/ea_profile.json
* 2023-02-16 02:20:54 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/DOolnrW7Lv/ea_profile.json
* 2023-02-16 02:20:54 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-16 02:20:55 (2727) [[33mWARN[0m] *** 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-16 02:20:56 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-17 02:18:26 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-17 02:18:27 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-17 02:18:27 (3898) [[32mINFO[0m] 
* 2023-02-17 02:18:28 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-17 02:18:28 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-17 02:18:28 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-17 02:18:28 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-17 02:18:28 (3912) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-17 02:18:28 (3929) [[32mINFO[0m] 
* 2023-02-17 02:18:28 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-17 02:18:28 (3898) [[32mINFO[0m] 
* 2023-02-17 02:19:00 (3929) [[32mINFO[0m] 
* 2023-02-17 02:19:01 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-17 02:19:01 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-17 02:19:01 (3898) [[32mINFO[0m] 
* 2023-02-17 02:19:01 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-17 02:19:02 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-17 02:19:02 (3929) [[32mINFO[0m] 
* 2023-02-17 02:19:02 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-17 02:19:02 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/A4MQzwmPoI/ea_profile.json
* 2023-02-17 02:19:04 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/A4MQzwmPoI/ea_profile.json
* 2023-02-17 02:19:04 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-17 02:19:05 (2727) [[33mWARN[0m] *** 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-17 02:19:05 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-17 15:48:10 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-17 15:48:10 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-17 15:48:10 (3898) [[32mINFO[0m] 
* 2023-02-17 15:48:10 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-17 15:48:10 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-17 15:48:10 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-17 15:48:11 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-17 15:48:11 (3912) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-17 15:48:11 (3929) [[32mINFO[0m] 
* 2023-02-17 15:48:11 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-17 15:48:11 (3898) [[32mINFO[0m] 
* 2023-02-17 15:48:46 (3929) [[32mINFO[0m] 
* 2023-02-17 15:48:46 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-17 15:48:46 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-17 15:48:46 (3898) [[32mINFO[0m] 
* 2023-02-17 15:48:47 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-17 15:48:48 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-17 15:48:48 (3929) [[32mINFO[0m] 
* 2023-02-17 15:48:48 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-17 15:48:48 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gRPY63fcXH/ea_profile.json
* 2023-02-17 15:48:49 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/gRPY63fcXH/ea_profile.json
* 2023-02-17 15:48:49 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-17 15:48:50 (2727) [[33mWARN[0m] *** 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-17 15:48:51 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-18 02:14:32 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-18 02:14:32 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-18 02:14:32 (3898) [[32mINFO[0m] 
* 2023-02-18 02:14:33 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-18 02:14:33 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-18 02:14:33 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-18 02:14:33 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-18 02:14:33 (3912) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-18 02:14:33 (3929) [[32mINFO[0m] 
* 2023-02-18 02:14:33 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-18 02:14:33 (3898) [[32mINFO[0m] 
* 2023-02-18 02:15:10 (3929) [[32mINFO[0m] 
* 2023-02-18 02:15:10 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-18 02:15:10 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-18 02:15:10 (3898) [[32mINFO[0m] 
* 2023-02-18 02:15:11 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-18 02:15:12 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-18 02:15:12 (3929) [[32mINFO[0m] 
* 2023-02-18 02:15:12 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-18 02:15:13 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PN9jMu8czU/ea_profile.json
* 2023-02-18 02:15:14 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/PN9jMu8czU/ea_profile.json
* 2023-02-18 02:15:14 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-18 02:15:16 (2727) [[33mWARN[0m] *** 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-18 02:15:16 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-19 02:14:47 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-19 02:14:47 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-19 02:14:47 (3898) [[32mINFO[0m] 
* 2023-02-19 02:14:48 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-19 02:14:48 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-19 02:14:48 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-19 02:14:48 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-19 02:14:48 (3912) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-19 02:14:48 (3929) [[32mINFO[0m] 
* 2023-02-19 02:14:48 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-19 02:14:48 (3898) [[32mINFO[0m] 
* 2023-02-19 02:15:35 (3929) [[32mINFO[0m] 
* 2023-02-19 02:15:35 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-19 02:15:35 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-19 02:15:35 (3898) [[32mINFO[0m] 
* 2023-02-19 02:15:40 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-19 02:15:42 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-19 02:15:43 (3929) [[32mINFO[0m] 
* 2023-02-19 02:15:43 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-19 02:15:43 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/b8f4Aunio4/ea_profile.json
* 2023-02-19 02:15:44 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/b8f4Aunio4/ea_profile.json
* 2023-02-19 02:15:44 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-19 02:15:45 (2727) [[33mWARN[0m] *** 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-19 02:15:45 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-20 02:13:40 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-20 02:13:42 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-20 02:13:42 (3898) [[32mINFO[0m] 
* 2023-02-20 02:13:42 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-20 02:13:42 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-20 02:13:42 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-20 02:13:42 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-20 02:13:42 (3912) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-20 02:13:42 (3929) [[32mINFO[0m] 
* 2023-02-20 02:13:42 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-20 02:13:42 (3898) [[32mINFO[0m] 
* 2023-02-20 02:14:20 (3929) [[32mINFO[0m] 
* 2023-02-20 02:14:20 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-20 02:14:20 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-20 02:14:20 (3898) [[32mINFO[0m] 
* 2023-02-20 02:14:20 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-20 02:14:21 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-20 02:14:21 (3929) [[32mINFO[0m] 
* 2023-02-20 02:14:21 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-20 02:14:21 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6JRs3qsgzo/ea_profile.json
* 2023-02-20 02:14:23 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/6JRs3qsgzo/ea_profile.json
* 2023-02-20 02:14:23 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-20 02:14:24 (2727) [[33mWARN[0m] *** 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-20 02:14:24 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-21 02:13:48 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-21 02:13:48 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-21 02:13:48 (3898) [[32mINFO[0m] 
* 2023-02-21 02:13:48 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-21 02:13:48 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-21 02:13:48 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-21 02:13:49 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-21 02:13:49 (3912) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-21 02:13:49 (3929) [[32mINFO[0m] 
* 2023-02-21 02:13:49 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-21 02:13:49 (3898) [[32mINFO[0m] 
* 2023-02-21 02:14:32 (3929) [[32mINFO[0m] 
* 2023-02-21 02:14:32 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-21 02:14:32 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-21 02:14:32 (3898) [[32mINFO[0m] 
* 2023-02-21 02:14:33 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-21 02:14:34 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-21 02:14:34 (3929) [[32mINFO[0m] 
* 2023-02-21 02:14:34 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-21 02:14:34 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AnHAJxiQ3Y/ea_profile.json
* 2023-02-21 02:14:35 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/AnHAJxiQ3Y/ea_profile.json
* 2023-02-21 02:14:35 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-21 02:14:36 (2727) [[33mWARN[0m] *** 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-21 02:14:36 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-22 02:14:11 (3385) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-22 02:14:11 (3897) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-22 02:14:11 (3898) [[32mINFO[0m] 
* 2023-02-22 02:14:12 (3912) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-22 02:14:12 (3912) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-22 02:14:12 (3912) [[32mINFO[0m]               : epel extras updates
* 2023-02-22 02:14:12 (3912) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-22 02:14:12 (3912) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-22 02:14:12 (3929) [[32mINFO[0m] 
* 2023-02-22 02:14:12 (3897) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-22 02:14:12 (3898) [[32mINFO[0m] 
* 2023-02-22 02:14:45 (3929) [[32mINFO[0m] 
* 2023-02-22 02:14:45 (3408) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-22 02:14:45 (3897) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-22 02:14:45 (3898) [[32mINFO[0m] 
* 2023-02-22 02:14:45 (3912) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-22 02:14:46 (3912) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-22 02:14:46 (3929) [[32mINFO[0m] 
* 2023-02-22 02:14:46 (3047) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-22 02:14:46 (1642) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oyvWEVWwWp/ea_profile.json
* 2023-02-22 02:14:48 (1667) [[32mINFO[0m] Backed up EA4 profile to /tmp/oyvWEVWwWp/ea_profile.json
* 2023-02-22 02:14:48 (2727) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-22 02:14:49 (2727) [[33mWARN[0m] *** 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-22 02:14:50 (709) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-24 02:18:44 (366) [[32mINFO[0m] Self-update of script version 4 requested.
* 2023-02-24 02:18:45 (371) [[32mINFO[0m] Newer version of script found. Downloading.
* 2023-02-24 02:18:46 (380) [[32mINFO[0m] Script update to version 5 successful.
* 2023-02-24 02:18:48 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-02-24 02:19:07 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-24 02:19:07 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-24 02:19:07 (4079) [[32mINFO[0m] 
* 2023-02-24 02:19:07 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-24 02:19:07 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-24 02:19:07 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-02-24 02:19:08 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-24 02:19:08 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-24 02:19:08 (4110) [[32mINFO[0m] 
* 2023-02-24 02:19:08 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-24 02:19:08 (4079) [[32mINFO[0m] 
* 2023-02-24 02:19:50 (4110) [[32mINFO[0m] 
* 2023-02-24 02:19:50 (3589) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-24 02:19:50 (4078) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-24 02:19:50 (4079) [[32mINFO[0m] 
* 2023-02-24 02:19:50 (4093) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-24 02:19:52 (4093) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-24 02:19:52 (4110) [[32mINFO[0m] 
* 2023-02-24 02:19:52 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-24 02:19:52 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bigDKUiEd2/ea_profile.json
* 2023-02-24 02:19:54 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/bigDKUiEd2/ea_profile.json
* 2023-02-24 02:19:54 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-24 02:19:57 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-24 15:51:52 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-02-24 15:53:49 (3733) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-02-24 15:53:49 (3734) [[31mERROR[0m] http://mirror.earthlink.iq/epel/7/x86_64/repodata/96feac1e997790d40454f9b919a2c18a843742387e9df6adcaede76996b1b17a-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.earthlink.iq/epel/7/x86_64/repodata/96feac1e997790d40454f9b919a2c18a843742387e9df6adcaede76996b1b17a-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
* 2023-02-24 15:53:49 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-02-24 15:53:50 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-24 15:53:50 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-24 15:53:50 (4079) [[32mINFO[0m] 
* 2023-02-24 15:53:50 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-24 15:53:50 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-24 15:53:50 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-02-24 15:53:51 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-24 15:53:51 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-24 15:53:51 (4110) [[32mINFO[0m] 
* 2023-02-24 15:53:51 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-24 15:53:51 (4079) [[32mINFO[0m] 
* 2023-02-24 15:54:40 (4110) [[32mINFO[0m] 
* 2023-02-24 15:54:40 (3589) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-24 15:54:40 (4078) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-24 15:54:40 (4079) [[32mINFO[0m] 
* 2023-02-24 15:54:40 (4093) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-24 15:54:42 (4093) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-24 15:54:42 (4110) [[32mINFO[0m] 
* 2023-02-24 15:54:42 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-24 15:54:42 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_T9n1mqVlF/ea_profile.json
* 2023-02-24 15:54:43 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/_T9n1mqVlF/ea_profile.json
* 2023-02-24 15:54:43 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-24 15:54:45 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-25 02:15:24 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-25 02:15:24 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-25 02:15:24 (4079) [[32mINFO[0m] 
* 2023-02-25 02:15:24 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-25 02:15:24 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-25 02:15:24 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-02-25 02:15:25 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-25 02:15:25 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-25 02:15:25 (4110) [[32mINFO[0m] 
* 2023-02-25 02:15:25 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-25 02:15:25 (4079) [[32mINFO[0m] 
* 2023-02-25 02:15:58 (4110) [[32mINFO[0m] 
* 2023-02-25 02:15:58 (3589) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-25 02:15:58 (4078) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-25 02:15:58 (4079) [[32mINFO[0m] 
* 2023-02-25 02:15:58 (4093) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-25 02:16:00 (4093) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-25 02:16:00 (4110) [[32mINFO[0m] 
* 2023-02-25 02:16:00 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-25 02:16:00 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4aY5xM3vYT/ea_profile.json
* 2023-02-25 02:16:01 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/4aY5xM3vYT/ea_profile.json
* 2023-02-25 02:16:01 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-25 02:16:04 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-26 02:20:41 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-02-26 02:21:32 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-26 02:21:32 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-26 02:21:32 (4079) [[32mINFO[0m] 
* 2023-02-26 02:21:32 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-26 02:21:32 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-26 02:21:32 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-02-26 02:21:33 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-26 02:21:33 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-26 02:21:33 (4110) [[32mINFO[0m] 
* 2023-02-26 02:21:33 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-26 02:21:33 (4079) [[32mINFO[0m] 
* 2023-02-26 02:22:03 (4093) [[32mINFO[0m] http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/d87d8d425620757f74beb23f12c9619ae9958ebdb364690b756e481ee6aab73a-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
* 2023-02-26 02:22:03 (4093) [[32mINFO[0m] Trying other mirror.
* 2023-02-26 02:22:22 (4093) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/a9c7a8cbffb5e5c07cbf31397bf11d9f7755e96c72ce897e04dba556dd4cc0eb-comps-Everything.x86_64.xml.gz: [Errno 12] Timeout on http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/a9c7a8cbffb5e5c07cbf31397bf11d9f7755e96c72ce897e04dba556dd4cc0eb-comps-Everything.x86_64.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-02-26 02:22:22 (4093) [[32mINFO[0m] Trying other mirror.
* 2023-02-26 02:23:19 (4093) [[32mINFO[0m] https://mirror.yer.az/fedora-epel/7/x86_64/repodata/52319e31a87e67d3b5c27c6997e1b4967a902996e5f6ed2d407fdfd497d46d15-primary.sqlite.bz2: [Errno 12] Timeout on https://mirror.yer.az/fedora-epel/7/x86_64/repodata/52319e31a87e67d3b5c27c6997e1b4967a902996e5f6ed2d407fdfd497d46d15-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-02-26 02:23:19 (4093) [[32mINFO[0m] Trying other mirror.
* 2023-02-26 02:23:35 (4110) [[32mINFO[0m] 
* 2023-02-26 02:23:35 (3589) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-26 02:23:35 (4078) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-26 02:23:35 (4079) [[32mINFO[0m] 
* 2023-02-26 02:23:35 (4093) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-26 02:23:38 (4093) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-26 02:23:38 (4110) [[32mINFO[0m] 
* 2023-02-26 02:23:38 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-26 02:23:38 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EYdmVCSyf0/ea_profile.json
* 2023-02-26 02:23:40 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/EYdmVCSyf0/ea_profile.json
* 2023-02-26 02:23:40 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-26 02:23:42 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-27 02:16:39 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-27 02:16:39 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-27 02:16:39 (4079) [[32mINFO[0m] 
* 2023-02-27 02:16:39 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-27 02:16:40 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-27 02:16:40 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-02-27 02:16:40 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-27 02:16:40 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-27 02:16:40 (4110) [[32mINFO[0m] 
* 2023-02-27 02:16:40 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-27 02:16:40 (4079) [[32mINFO[0m] 
* 2023-02-27 02:17:13 (4110) [[32mINFO[0m] 
* 2023-02-27 02:17:13 (3589) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-27 02:17:13 (4078) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-27 02:17:13 (4079) [[32mINFO[0m] 
* 2023-02-27 02:17:13 (4093) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-27 02:17:14 (4093) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-27 02:17:14 (4110) [[32mINFO[0m] 
* 2023-02-27 02:17:14 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-27 02:17:17 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/anCK7b12Zc/ea_profile.json
* 2023-02-27 02:17:19 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/anCK7b12Zc/ea_profile.json
* 2023-02-27 02:17:19 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-27 02:17:21 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-02-28 02:16:00 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-02-28 02:16:00 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-02-28 02:16:00 (4079) [[32mINFO[0m] 
* 2023-02-28 02:16:01 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-28 02:16:01 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-02-28 02:16:01 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-02-28 02:16:01 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-02-28 02:16:01 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-02-28 02:16:01 (4110) [[32mINFO[0m] 
* 2023-02-28 02:16:01 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-02-28 02:16:01 (4079) [[32mINFO[0m] 
* 2023-02-28 02:16:37 (4110) [[32mINFO[0m] 
* 2023-02-28 02:16:37 (3589) [[32mINFO[0m] Checking /scripts/sysup
* 2023-02-28 02:16:37 (4078) [[32mINFO[0m] Running: /scripts/sysup
* 2023-02-28 02:16:37 (4079) [[32mINFO[0m] 
* 2023-02-28 02:16:37 (4093) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-02-28 02:16:39 (4093) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-02-28 02:16:39 (4110) [[32mINFO[0m] 
* 2023-02-28 02:16:39 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-28 02:16:39 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mpk6Zt0DzU/ea_profile.json
* 2023-02-28 02:16:41 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/mpk6Zt0DzU/ea_profile.json
* 2023-02-28 02:16:41 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-02-28 02:16:43 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-01 02:15:48 (3733) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-03-01 02:15:48 (3734) [[31mERROR[0m] http://102.22.80.80/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/a168648430654a927dcc94a55c38cf2253df920819831ba8a746fe09d0907684-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://102.22.80.80/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/06ab67df09fb1418dd17c74496459160679d06c19f2bb9959711c18547afdaf9-other.sqlite.bz2: [Errno 12] Timeout on http://102.22.80.80/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/06ab67df09fb1418dd17c74496459160679d06c19f2bb9959711c18547afdaf9-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.101.161.235/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/06ab67df09fb1418dd17c74496459160679d06c19f2bb9959711c18547afdaf9-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-03-01 02:15:48 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-01 02:15:49 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-01 02:15:49 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-01 02:15:49 (4079) [[32mINFO[0m] 
* 2023-03-01 02:15:49 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-01 02:15:49 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-01 02:15:49 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-03-01 02:15:50 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-01 02:15:50 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-01 02:15:50 (4110) [[32mINFO[0m] 
* 2023-03-01 02:15:50 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-01 02:15:50 (4079) [[32mINFO[0m] 
* 2023-03-01 02:16:34 (4110) [[32mINFO[0m] 
* 2023-03-01 02:16:34 (3589) [[32mINFO[0m] Checking /scripts/sysup
* 2023-03-01 02:16:34 (4078) [[32mINFO[0m] Running: /scripts/sysup
* 2023-03-01 02:16:34 (4079) [[32mINFO[0m] 
* 2023-03-01 02:16:35 (4093) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-03-01 02:16:36 (4093) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-03-01 02:16:36 (4110) [[32mINFO[0m] 
* 2023-03-01 02:16:36 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-01 02:16:36 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ybiMsbYFpj/ea_profile.json
* 2023-03-01 02:16:38 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/ybiMsbYFpj/ea_profile.json
* 2023-03-01 02:16:38 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-01 02:16:40 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-02 02:14:52 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-02 02:14:52 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-02 02:14:52 (4079) [[32mINFO[0m] 
* 2023-03-02 02:14:52 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-02 02:14:52 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-02 02:14:52 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-03-02 02:14:52 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-02 02:14:52 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-02 02:14:52 (4110) [[32mINFO[0m] 
* 2023-03-02 02:14:52 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-02 02:14:52 (4079) [[32mINFO[0m] 
* 2023-03-02 02:15:24 (4110) [[32mINFO[0m] 
* 2023-03-02 02:15:24 (3589) [[32mINFO[0m] Checking /scripts/sysup
* 2023-03-02 02:15:24 (4078) [[32mINFO[0m] Running: /scripts/sysup
* 2023-03-02 02:15:24 (4079) [[32mINFO[0m] 
* 2023-03-02 02:15:24 (4093) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-03-02 02:15:25 (4093) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-03-02 02:15:25 (4110) [[32mINFO[0m] 
* 2023-03-02 02:15:25 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-02 02:15:25 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/v15VRU_nB7/ea_profile.json
* 2023-03-02 02:15:27 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/v15VRU_nB7/ea_profile.json
* 2023-03-02 02:15:27 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-02 02:15:29 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-03 02:17:58 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-03 02:17:58 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-03 02:17:58 (4079) [[32mINFO[0m] 
* 2023-03-03 02:17:58 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-03 02:17:58 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-03 02:17:58 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-03-03 02:17:59 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-03 02:17:59 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-03 02:17:59 (4110) [[32mINFO[0m] 
* 2023-03-03 02:17:59 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-03 02:17:59 (4079) [[32mINFO[0m] 
* 2023-03-03 02:19:04 (4093) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/83b3dba22da4dcbd09bf0e6eeda6a9718caf55f46ea7a7f9c0446dfb3ef66fe0-comps-Everything.x86_64.xml.gz: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/83b3dba22da4dcbd09bf0e6eeda6a9718caf55f46ea7a7f9c0446dfb3ef66fe0-comps-Everything.x86_64.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-03-03 02:19:04 (4093) [[32mINFO[0m] Trying other mirror.
* 2023-03-03 02:19:39 (4093) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/26c8cc88c33c13f9abdd595225a5be5151d6e978291947817ecec1d54f0f5c90-primary.sqlite.bz2: [Errno 12] Timeout on http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/26c8cc88c33c13f9abdd595225a5be5151d6e978291947817ecec1d54f0f5c90-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-03-03 02:19:39 (4093) [[32mINFO[0m] Trying other mirror.
* 2023-03-03 02:19:58 (4110) [[32mINFO[0m] 
* 2023-03-03 02:19:58 (3589) [[32mINFO[0m] Checking /scripts/sysup
* 2023-03-03 02:19:58 (4078) [[32mINFO[0m] Running: /scripts/sysup
* 2023-03-03 02:19:58 (4079) [[32mINFO[0m] 
* 2023-03-03 02:19:58 (4093) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-03-03 02:20:00 (4093) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-03-03 02:20:00 (4110) [[32mINFO[0m] 
* 2023-03-03 02:20:00 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-03 02:20:00 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nMvCchNnRH/ea_profile.json
* 2023-03-03 02:20:02 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/nMvCchNnRH/ea_profile.json
* 2023-03-03 02:20:02 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-03 02:20:05 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-04 02:14:52 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-04 02:14:52 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-04 02:14:52 (4079) [[32mINFO[0m] 
* 2023-03-04 02:14:53 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-04 02:14:53 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-04 02:14:53 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-03-04 02:14:53 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-04 02:14:53 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-04 02:14:53 (4110) [[32mINFO[0m] 
* 2023-03-04 02:14:53 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-04 02:14:53 (4079) [[32mINFO[0m] 
* 2023-03-04 02:15:27 (4110) [[32mINFO[0m] 
* 2023-03-04 02:15:27 (3589) [[32mINFO[0m] Checking /scripts/sysup
* 2023-03-04 02:15:27 (4078) [[32mINFO[0m] Running: /scripts/sysup
* 2023-03-04 02:15:27 (4079) [[32mINFO[0m] 
* 2023-03-04 02:15:27 (4093) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-03-04 02:15:29 (4093) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-03-04 02:15:29 (4110) [[32mINFO[0m] 
* 2023-03-04 02:15:29 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-04 02:15:29 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cXLADWlqS5/ea_profile.json
* 2023-03-04 02:15:31 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/cXLADWlqS5/ea_profile.json
* 2023-03-04 02:15:31 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-04 02:15:33 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-05 02:14:22 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-05 02:14:22 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-05 02:14:22 (4079) [[32mINFO[0m] 
* 2023-03-05 02:14:22 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-05 02:14:23 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-05 02:14:23 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-03-05 02:14:23 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-05 02:14:23 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-05 02:14:23 (4110) [[32mINFO[0m] 
* 2023-03-05 02:14:23 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-05 02:14:23 (4079) [[32mINFO[0m] 
* 2023-03-05 02:14:59 (4110) [[32mINFO[0m] 
* 2023-03-05 02:14:59 (3589) [[32mINFO[0m] Checking /scripts/sysup
* 2023-03-05 02:14:59 (4078) [[32mINFO[0m] Running: /scripts/sysup
* 2023-03-05 02:14:59 (4079) [[32mINFO[0m] 
* 2023-03-05 02:14:59 (4093) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-03-05 02:15:00 (4093) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-03-05 02:15:00 (4110) [[32mINFO[0m] 
* 2023-03-05 02:15:00 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-05 02:15:00 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Qdc59X2Trv/ea_profile.json
* 2023-03-05 02:15:02 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/Qdc59X2Trv/ea_profile.json
* 2023-03-05 02:15:02 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-05 02:15:04 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-06 02:16:06 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-03-06 02:16:23 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-06 02:16:23 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-06 02:16:23 (4079) [[32mINFO[0m] 
* 2023-03-06 02:16:23 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-06 02:16:23 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-06 02:16:23 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-03-06 02:16:23 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-06 02:16:23 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-06 02:16:23 (4110) [[32mINFO[0m] 
* 2023-03-06 02:16:23 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-06 02:16:23 (4079) [[32mINFO[0m] 
* 2023-03-06 02:16:56 (4110) [[32mINFO[0m] 
* 2023-03-06 02:16:56 (3589) [[32mINFO[0m] Checking /scripts/sysup
* 2023-03-06 02:16:56 (4078) [[32mINFO[0m] Running: /scripts/sysup
* 2023-03-06 02:16:56 (4079) [[32mINFO[0m] 
* 2023-03-06 02:16:56 (4093) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-03-06 02:16:58 (4093) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-03-06 02:16:58 (4110) [[32mINFO[0m] 
* 2023-03-06 02:16:58 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-06 02:16:58 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sfdJNte5El/ea_profile.json
* 2023-03-06 02:16:59 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/sfdJNte5El/ea_profile.json
* 2023-03-06 02:16:59 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-06 02:17:01 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-07 02:13:45 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-07 02:13:45 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-07 02:13:45 (4079) [[32mINFO[0m] 
* 2023-03-07 02:13:45 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-07 02:13:45 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-07 02:13:45 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-03-07 02:13:45 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-07 02:13:45 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-07 02:13:45 (4110) [[32mINFO[0m] 
* 2023-03-07 02:13:45 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-07 02:13:45 (4079) [[32mINFO[0m] 
* 2023-03-07 02:14:15 (4110) [[32mINFO[0m] 
* 2023-03-07 02:14:15 (3589) [[32mINFO[0m] Checking /scripts/sysup
* 2023-03-07 02:14:15 (4078) [[32mINFO[0m] Running: /scripts/sysup
* 2023-03-07 02:14:16 (4079) [[32mINFO[0m] 
* 2023-03-07 02:14:16 (4093) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-03-07 02:14:17 (4093) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-03-07 02:14:17 (4110) [[32mINFO[0m] 
* 2023-03-07 02:14:17 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-07 02:14:17 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LTEZ_5ClXm/ea_profile.json
* 2023-03-07 02:14:19 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/LTEZ_5ClXm/ea_profile.json
* 2023-03-07 02:14:19 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-07 02:14:21 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-08 02:16:53 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-08 02:16:53 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-08 02:16:53 (4079) [[32mINFO[0m] 
* 2023-03-08 02:16:54 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-08 02:16:54 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-08 02:16:54 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-03-08 02:16:54 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-08 02:16:54 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-08 02:16:54 (4110) [[32mINFO[0m] 
* 2023-03-08 02:16:54 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-08 02:16:54 (4079) [[32mINFO[0m] 
* 2023-03-08 02:17:27 (4110) [[32mINFO[0m] 
* 2023-03-08 02:17:27 (3589) [[32mINFO[0m] Checking /scripts/sysup
* 2023-03-08 02:17:27 (4078) [[32mINFO[0m] Running: /scripts/sysup
* 2023-03-08 02:17:27 (4079) [[32mINFO[0m] 
* 2023-03-08 02:17:28 (4093) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-03-08 02:17:30 (4093) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-03-08 02:17:30 (4110) [[32mINFO[0m] 
* 2023-03-08 02:17:30 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-08 02:17:30 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oXGtMMLFI6/ea_profile.json
* 2023-03-08 02:17:32 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/oXGtMMLFI6/ea_profile.json
* 2023-03-08 02:17:32 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-08 02:17:34 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-09 02:18:59 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-09 02:18:59 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-09 02:18:59 (4079) [[32mINFO[0m] 
* 2023-03-09 02:18:59 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-09 02:19:00 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-09 02:19:00 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-03-09 02:19:00 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-09 02:19:00 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-09 02:19:00 (4110) [[32mINFO[0m] 
* 2023-03-09 02:19:00 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-09 02:19:00 (4079) [[32mINFO[0m] 
* 2023-03-09 02:19:34 (4093) [[32mINFO[0m] 
* 2023-03-09 02:19:34 (4093) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-09 02:19:35 (4110) [[32mINFO[0m] 
* 2023-03-09 02:19:35 (3574) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-09 02:19:35 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-09 02:19:35 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-09 02:19:36 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lCE_2UmmjX/ea_profile.json
* 2023-03-09 02:19:37 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/lCE_2UmmjX/ea_profile.json
* 2023-03-09 02:19:37 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-09 02:19:41 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-10 02:14:08 (3733) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-03-10 02:14:08 (3734) [[31mERROR[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/cpanel-plugins-c7-x86_64-mirrorlist error was
12: Timeout on http://httpupdate.cpanel.net/cpanel-plugins-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-03-10 02:14:08 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-10 02:14:08 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-10 02:14:08 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-10 02:14:08 (4079) [[32mINFO[0m] 
* 2023-03-10 02:14:08 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-10 02:14:09 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-10 02:14:09 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-03-10 02:14:09 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-10 02:14:09 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-10 02:14:09 (4110) [[32mINFO[0m] 
* 2023-03-10 02:14:09 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-10 02:14:09 (4079) [[32mINFO[0m] 
* 2023-03-10 02:14:50 (4093) [[32mINFO[0m] 
* 2023-03-10 02:14:50 (4093) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-10 02:14:50 (4110) [[32mINFO[0m] 
* 2023-03-10 02:14:50 (3574) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-10 02:14:50 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-10 02:14:50 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-10 02:14:50 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zPzlb0b906/ea_profile.json
* 2023-03-10 02:14:52 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/zPzlb0b906/ea_profile.json
* 2023-03-10 02:14:52 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-10 02:14:54 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-10 15:51:35 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-10 15:51:35 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-10 15:51:35 (4079) [[32mINFO[0m] 
* 2023-03-10 15:51:35 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-10 15:51:35 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-10 15:51:35 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-03-10 15:51:36 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-10 15:51:36 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-10 15:51:36 (4110) [[32mINFO[0m] 
* 2023-03-10 15:51:36 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-10 15:51:36 (4079) [[32mINFO[0m] 
* 2023-03-10 15:52:12 (4093) [[32mINFO[0m] 
* 2023-03-10 15:52:12 (4093) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-10 15:52:12 (4110) [[32mINFO[0m] 
* 2023-03-10 15:52:12 (3574) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-10 15:52:12 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-10 15:52:12 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-10 15:52:12 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qlvtnpDdMF/ea_profile.json
* 2023-03-10 15:52:13 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/qlvtnpDdMF/ea_profile.json
* 2023-03-10 15:52:13 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-10 15:52:15 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-11 02:15:16 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-11 02:15:16 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-11 02:15:16 (4079) [[32mINFO[0m] 
* 2023-03-11 02:15:16 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-11 02:15:17 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-11 02:15:17 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-03-11 02:15:17 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-11 02:15:17 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-11 02:15:17 (4110) [[32mINFO[0m] 
* 2023-03-11 02:15:17 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-11 02:15:17 (4079) [[32mINFO[0m] 
* 2023-03-11 02:15:47 (4093) [[32mINFO[0m] 
* 2023-03-11 02:15:47 (4093) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-11 02:15:47 (4110) [[32mINFO[0m] 
* 2023-03-11 02:15:47 (3574) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-11 02:15:47 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-11 02:15:47 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-11 02:15:47 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lYVIs5aU_u/ea_profile.json
* 2023-03-11 02:15:49 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/lYVIs5aU_u/ea_profile.json
* 2023-03-11 02:15:49 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-11 02:15:51 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-12 02:18:47 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-12 02:18:47 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-12 02:18:47 (4079) [[32mINFO[0m] 
* 2023-03-12 02:18:47 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-12 02:18:47 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-12 02:18:47 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-03-12 02:18:47 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-12 02:18:47 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-12 02:18:47 (4110) [[32mINFO[0m] 
* 2023-03-12 02:18:47 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-12 02:18:47 (4079) [[32mINFO[0m] 
* 2023-03-12 02:19:16 (4093) [[32mINFO[0m] 
* 2023-03-12 02:19:16 (4093) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-12 02:19:16 (4110) [[32mINFO[0m] 
* 2023-03-12 02:19:16 (3574) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-12 02:19:16 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-12 02:19:16 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-12 02:19:16 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/W731nA5C47/ea_profile.json
* 2023-03-12 02:19:17 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/W731nA5C47/ea_profile.json
* 2023-03-12 02:19:17 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-12 02:20:18 (2716) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 65u7z7) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> “GET” request to “https://raw.githubusercontent.com/cpanel/elevate/release/version” because of an error: SSL connection failed for raw.githubusercontent.com: SSL wants a read first
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x3a01290), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3a010e0)) called at (eval 12) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x3a01290), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 3292
	cpev::latest_version(cpev=HASH(0x261a458)) called at /usr/local/cpanel/scripts/elevate-cpanel line 3272
	cpev::is_script_out_of_date(cpev=HASH(0x261a458)) called at /usr/local/cpanel/scripts/elevate-cpanel line 3258
	cpev::_blocker_script_updated(cpev=HASH(0x261a458)) called at /usr/local/cpanel/scripts/elevate-cpanel line 3554
	cpev::_blockers_check(cpev=HASH(0x261a458)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2707
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 2706
	cpev::blockers_check(cpev=HASH(0x261a458), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 709
	cpev::do_check(cpev=HASH(0x261a458)) called at /usr/local/cpanel/scripts/elevate-cpanel line 319
	cpev::run(cpev=HASH(0x261a458)) called at /usr/local/cpanel/scripts/elevate-cpanel line 291
* 2023-03-12 02:20:18 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-13 02:20:59 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-13 02:20:59 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-13 02:20:59 (4079) [[32mINFO[0m] 
* 2023-03-13 02:21:00 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-13 02:21:00 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-13 02:21:00 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-03-13 02:21:00 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-13 02:21:00 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-13 02:21:00 (4110) [[32mINFO[0m] 
* 2023-03-13 02:21:00 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-13 02:21:00 (4079) [[32mINFO[0m] 
* 2023-03-13 02:21:29 (4093) [[32mINFO[0m] 
* 2023-03-13 02:21:29 (4093) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-13 02:21:29 (4110) [[32mINFO[0m] 
* 2023-03-13 02:21:29 (3574) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-13 02:21:29 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-13 02:21:29 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-13 02:21:29 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6HzZnPwhGS/ea_profile.json
* 2023-03-13 02:21:30 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/6HzZnPwhGS/ea_profile.json
* 2023-03-13 02:21:30 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-13 02:22:31 (2716) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID xdxhv8) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> “GET” request to “https://raw.githubusercontent.com/cpanel/elevate/release/version” because of an error: SSL connection failed for raw.githubusercontent.com: SSL wants a read first
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x1bb60d0), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x1bb6160)) called at (eval 12) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x1bb60d0), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 3292
	cpev::latest_version(cpev=HASH(0x7bf448)) called at /usr/local/cpanel/scripts/elevate-cpanel line 3272
	cpev::is_script_out_of_date(cpev=HASH(0x7bf448)) called at /usr/local/cpanel/scripts/elevate-cpanel line 3258
	cpev::_blocker_script_updated(cpev=HASH(0x7bf448)) called at /usr/local/cpanel/scripts/elevate-cpanel line 3554
	cpev::_blockers_check(cpev=HASH(0x7bf448)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2707
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 2706
	cpev::blockers_check(cpev=HASH(0x7bf448), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 709
	cpev::do_check(cpev=HASH(0x7bf448)) called at /usr/local/cpanel/scripts/elevate-cpanel line 319
	cpev::run(cpev=HASH(0x7bf448)) called at /usr/local/cpanel/scripts/elevate-cpanel line 291
* 2023-03-13 02:22:31 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-14 02:19:41 (3733) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-03-14 02:19:41 (3734) [[31mERROR[0m] http://103.252.152.1/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/d813c27fae98618fbbba4e613c3ee0f1b341074ee8670428abdf8fb6a6f3535b-filelists.sqlite.bz2: [Errno 12] Timeout on http://103.252.152.1/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/d813c27fae98618fbbba4e613c3ee0f1b341074ee8670428abdf8fb6a6f3535b-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.94/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.94/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://185.15.22.168/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: [Errno 12] Timeout on http://185.15.22.168/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://45.234.92.141/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/345917e162601ff600dc0c0f3120ca9875771ea6a1d3ed8ec1423464ca99ec3f-primary.sqlite.bz2: [Errno 12] Timeout on http://45.234.92.141/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/345917e162601ff600dc0c0f3120ca9875771ea6a1d3ed8ec1423464ca99ec3f-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.74.123.61/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/06ab67df09fb1418dd17c74496459160679d06c19f2bb9959711c18547afdaf9-other.sqlite.bz2: [Errno 12] Timeout on http://208.74.123.61/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/06ab67df09fb1418dd17c74496459160679d06c19f2bb9959711c18547afdaf9-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://centos.vargonen.com/centos/7.9.2009/updates/x86_64/repodata/bc8950506fb13622afd9eb93c811884b6e2e7570afd5fac946f708ac01ae0cff-primary.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
Trying other mirror.
http://centos.vargonen.com/centos/7.9.2009/updates/x86_64/repodata/07b8602634b5cbac7f8388d06be56f28723393ab172b028ff7ad8d5bd57f2e59-filelists.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
Trying other mirror.
http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/06ab67df09fb1418dd17c74496459160679d06c19f2bb9959711c18547afdaf9-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/345917e162601ff600dc0c0f3120ca9875771ea6a1d3ed8ec1423464ca99ec3f-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://mirror.verinomi.com/centos/7.9.2009/extras/x86_64/repodata/78c0e5530bc46d128e18eca9ff16b2d0651efdb33434408f8ff1db4d14f1bb99-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.verinomi.com/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.
http://mirror.verinomi.com/centos/7.9.2009/updates/x86_64/repodata/33c5109226f2c5e469c8519c6102af5a7fe9fa4064ef8621e296da454197f370-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.verinomi.com/centos/7.9.2009/updates/x86_64/repodata/33c5109226f2c5e469c8519c6102af5a7fe9fa4064ef8621e296da454197f370-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://84.95.247.234/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/d813c27fae98618fbbba4e613c3ee0f1b341074ee8670428abdf8fb6a6f3535b-filelists.sqlite.bz2: [Errno 12] Timeout on http://84.95.247.234/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/d813c27fae98618fbbba4e613c3ee0f1b341074ee8670428abdf8fb6a6f3535b-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirror.bursabil.com.tr/centos/7.9.2009/updates/x86_64/repodata/bc8950506fb13622afd9eb93c811884b6e2e7570afd5fac946f708ac01ae0cff-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.bursabil.com.tr/centos/7.9.2009/updates/x86_64/repodata/bc8950506fb13622afd9eb93c811884b6e2e7570afd5fac946f708ac01ae0cff-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/d813c27fae98618fbbba4e613c3ee0f1b341074ee8670428abdf8fb6a6f3535b-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://118.88.24.67/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://74.50.120.123/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/345917e162601ff600dc0c0f3120ca9875771ea6a1d3ed8ec1423464ca99ec3f-primary.sqlite.bz2: [Errno 12] Timeout on http://74.50.120.123/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/345917e162601ff600dc0c0f3120ca9875771ea6a1d3ed8ec1423464ca99ec3f-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://centos.vargonen.com/centos/7.9.2009/updates/x86_64/repodata/33c5109226f2c5e469c8519c6102af5a7fe9fa4064ef8621e296da454197f370-other.sqlite.bz2: [Errno 12] Timeout on http://centos.vargonen.com/centos/7.9.2009/updates/x86_64/repodata/33c5109226f2c5e469c8519c6102af5a7fe9fa4064ef8621e296da454197f370-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.17.8.8/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://103.17.8.8/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/345917e162601ff600dc0c0f3120ca9875771ea6a1d3ed8ec1423464ca99ec3f-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://185.125.185.32/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/345917e162601ff600dc0c0f3120ca9875771ea6a1d3ed8ec1423464ca99ec3f-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://185.125.185.32/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: [Errno 12] Timeout on http://185.125.185.32/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.100.0.204/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/345917e162601ff600dc0c0f3120ca9875771ea6a1d3ed8ec1423464ca99ec3f-primary.sqlite.bz2: [Errno 12] Timeout on http://208.100.0.204/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/345917e162601ff600dc0c0f3120ca9875771ea6a1d3ed8ec1423464ca99ec3f-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://184.94.196.92/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/345917e162601ff600dc0c0f3120ca9875771ea6a1d3ed8ec1423464ca99ec3f-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://184.94.196.92/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://31.22.112.31/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/345917e162601ff600dc0c0f3120ca9875771ea6a1d3ed8ec1423464ca99ec3f-primary.sqlite.bz2: [Errno 12] Timeout on http://31.22.112.31/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/345917e162601ff600dc0c0f3120ca9875771ea6a1d3ed8ec1423464ca99ec3f-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://201.159.169.169/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/345917e162601ff600dc0c0f3120ca9875771ea6a1d3ed8ec1423464ca99ec3f-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-03-14 02:19:41 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-14 02:19:41 (3566) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-14 02:19:41 (4078) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-14 02:19:41 (4079) [[32mINFO[0m] 
* 2023-03-14 02:19:41 (4093) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-14 02:19:42 (4093) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-14 02:19:42 (4093) [[32mINFO[0m]               : epel extras updates
* 2023-03-14 02:19:42 (4093) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-14 02:19:42 (4093) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-14 02:19:42 (4110) [[32mINFO[0m] 
* 2023-03-14 02:19:42 (4078) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-14 02:19:42 (4079) [[32mINFO[0m] 
* 2023-03-14 02:20:07 (4093) [[32mINFO[0m] http://mirror.bursabil.com.tr/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2a04:3880:0:16::205: Network is unreachable"
* 2023-03-14 02:20:07 (4093) [[32mINFO[0m] Trying other mirror.
* 2023-03-14 02:20:44 (4093) [[32mINFO[0m] 
* 2023-03-14 02:20:44 (4093) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-14 02:20:44 (4110) [[32mINFO[0m] 
* 2023-03-14 02:20:44 (3574) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-14 02:20:44 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-14 02:20:44 (3227) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-14 02:20:44 (1669) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/X2P0e4n26e/ea_profile.json
* 2023-03-14 02:20:46 (1694) [[32mINFO[0m] Backed up EA4 profile to /tmp/X2P0e4n26e/ea_profile.json
* 2023-03-14 02:20:46 (2749) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-14 02:21:46 (2716) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 43y8pa) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> “GET” request to “https://raw.githubusercontent.com/cpanel/elevate/release/version” because of an error: SSL connection failed for raw.githubusercontent.com: SSL wants a read first
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2c6e530), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2c6e2c0)) called at (eval 12) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2c6e530), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 3292
	cpev::latest_version(cpev=HASH(0x18584d8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 3272
	cpev::is_script_out_of_date(cpev=HASH(0x18584d8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 3258
	cpev::_blocker_script_updated(cpev=HASH(0x18584d8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 3554
	cpev::_blockers_check(cpev=HASH(0x18584d8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2707
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 2706
	cpev::blockers_check(cpev=HASH(0x18584d8), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 709
	cpev::do_check(cpev=HASH(0x18584d8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 319
	cpev::run(cpev=HASH(0x18584d8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 291
* 2023-03-14 02:21:46 (713) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-15 02:15:03 (368) [[32mINFO[0m] Self-update of script version 5 requested.
* 2023-03-15 02:15:03 (373) [[32mINFO[0m] Newer version of script found. Downloading.
* 2023-03-15 02:15:04 (382) [[32mINFO[0m] Script update to version 6 successful.
* 2023-03-15 02:20:30 (3805) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-03-15 02:20:30 (3806) [[31mERROR[0m] http://203.174.85.202/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno 12] Timeout on http://178.18.193.52/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/458ff0677e8f8e1e0a7c4ea53f4b0afe5fa722a7ae5280c8428e87994b3762f3-filelists.sqlite.bz2: [Errno 12] Timeout on http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/458ff0677e8f8e1e0a7c4ea53f4b0afe5fa722a7ae5280c8428e87994b3762f3-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/7d1b72ef50d2443e38471b1c37027a9336a13865e1840754522b4c1739664066-filelists.sqlite.bz2: [Errno 12] Timeout on http://178.18.193.52/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/7d1b72ef50d2443e38471b1c37027a9336a13865e1840754522b4c1739664066-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno 12] Timeout on http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://102.22.80.80/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/345917e162601ff600dc0c0f3120ca9875771ea6a1d3ed8ec1423464ca99ec3f-primary.sqlite.bz2: [Errno 12] Timeout on http://102.22.80.80/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/345917e162601ff600dc0c0f3120ca9875771ea6a1d3ed8ec1423464ca99ec3f-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.120.66.133/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/06ab67df09fb1418dd17c74496459160679d06c19f2bb9959711c18547afdaf9-other.sqlite.bz2: [Errno 12] Timeout on http://103.120.66.133/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/06ab67df09fb1418dd17c74496459160679d06c19f2bb9959711c18547afdaf9-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/0a834881fe83a80f211e331b8939036b9f029ad9a2df7af21628aa74c19d8523-filelists.sqlite.bz2: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/0a834881fe83a80f211e331b8939036b9f029ad9a2df7af21628aa74c19d8523-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/cd22cff0891016e22ba83bd9f4a06a0b837a3c387a2daea303f4397147952feb-updateinfo.xml.bz2: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/cd22cff0891016e22ba83bd9f4a06a0b837a3c387a2daea303f4397147952feb-updateinfo.xml.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/6f469b2d0b412cc1c87d2a17b7766a6d06f8b811e5a4268c9bfba930675f0b40-prestodelta.xml.gz: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/6f469b2d0b412cc1c87d2a17b7766a6d06f8b811e5a4268c9bfba930675f0b40-prestodelta.xml.gz: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')
Trying other mirror.
http://184.94.196.97/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/7d1b72ef50d2443e38471b1c37027a9336a13865e1840754522b4c1739664066-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://184.94.196.97/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/345917e162601ff600dc0c0f3120ca9875771ea6a1d3ed8ec1423464ca99ec3f-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://184.94.196.97/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/06ab67df09fb1418dd17c74496459160679d06c19f2bb9959711c18547afdaf9-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://mirror.01link.hk/epel/7/x86_64/repodata/cd22cff0891016e22ba83bd9f4a06a0b837a3c387a2daea303f4397147952feb-updateinfo.xml.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
It was impossible to connect to the CentOS servers.
This could mean a connectivity issue in your environment, such as the requirement to configure a proxy,
or a transparent proxy that tampers with TLS security, or an incorrect system clock.
You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors
If above article doesn't help to resolve this issue please use https://bugs.centos.org/.

http://103.48.119.120/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: [Errno 12] Timeout on http://103.48.119.120/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/cd22cff0891016e22ba83bd9f4a06a0b837a3c387a2daea303f4397147952feb-updateinfo.xml.bz2: [Errno 12] Timeout on https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/cd22cff0891016e22ba83bd9f4a06a0b837a3c387a2daea303f4397147952feb-updateinfo.xml.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://185.157.208.252/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: [Errno 12] Timeout on http://185.157.208.252/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.101.161.235/cpanelsync/repos/CentOS/7/EA4/repodata/fb63e08ca895ae4dcf3e75160297bd4b4de7fa5244265d927eafa9ea14d72d0d-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-03-15 02:20:30 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-15 02:20:31 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-15 02:20:31 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-15 02:20:31 (4151) [[32mINFO[0m] 
* 2023-03-15 02:20:31 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-15 02:20:31 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-15 02:20:31 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-15 02:20:31 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-15 02:20:31 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-15 02:20:31 (4182) [[32mINFO[0m] 
* 2023-03-15 02:20:31 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-15 02:20:31 (4151) [[32mINFO[0m] 
* 2023-03-15 02:21:11 (4165) [[32mINFO[0m] 
* 2023-03-15 02:21:11 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-15 02:21:11 (4182) [[32mINFO[0m] 
* 2023-03-15 02:21:11 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-15 02:21:11 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-15 02:21:11 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-15 02:21:11 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/CIjv2IAciL/ea_profile.json
* 2023-03-15 02:21:13 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/CIjv2IAciL/ea_profile.json
* 2023-03-15 02:21:13 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-15 02:21:14 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-16 02:22:11 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-16 02:22:11 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-16 02:22:11 (4151) [[32mINFO[0m] 
* 2023-03-16 02:22:11 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-16 02:22:11 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-16 02:22:11 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-16 02:22:11 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-16 02:22:11 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-16 02:22:11 (4182) [[32mINFO[0m] 
* 2023-03-16 02:22:11 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-16 02:22:11 (4151) [[32mINFO[0m] 
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m] 14: curl#52 - "Empty reply from server"
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m] 
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m] 
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m] 
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m] 
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m] 
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m] 
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m] 
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]         or
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m] 
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]         compromise:
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m] 
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m] 
* 2023-03-16 02:22:17 (4165) [[32mINFO[0m] Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2023-03-16 02:22:18 (4182) [[32mINFO[0m] 
* 2023-03-16 02:22:18 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-16 02:22:18 (3661) [[32mINFO[0m] Checking /scripts/sysup
* 2023-03-16 02:22:18 (4150) [[32mINFO[0m] Running: /scripts/sysup
* 2023-03-16 02:22:18 (4151) [[32mINFO[0m] 
* 2023-03-16 02:22:18 (4165) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-03-16 02:22:19 (4165) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-03-16 02:22:19 (4182) [[32mINFO[0m] 
* 2023-03-16 02:22:19 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-16 02:22:19 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XxtlKRpcri/ea_profile.json
* 2023-03-16 02:25:23 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/XxtlKRpcri/ea_profile.json
* 2023-03-16 02:25:23 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-16 02:25:24 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-17 02:28:57 (3805) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-03-17 02:28:57 (3806) [[31mERROR[0m] http://184.94.196.94/cpanelsync/repos/CentOS/7/EA4/repodata/repomd.xml: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/repomd.xml: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://103.72.162.35/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno 12] Timeout on http://103.72.162.35/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.93/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/8cd8bc2d2fc918c315046b553e84ce4da0469b3a457957dc329556907e5d325d-filelists.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.93/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/8cd8bc2d2fc918c315046b553e84ce4da0469b3a457957dc329556907e5d325d-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/458ff0677e8f8e1e0a7c4ea53f4b0afe5fa722a7ae5280c8428e87994b3762f3-filelists.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/458ff0677e8f8e1e0a7c4ea53f4b0afe5fa722a7ae5280c8428e87994b3762f3-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/8e8da7fca114e0273cb5f96fa7b7142b65a6f103e3c4e6a24a38fd39c185e178-filelists.sqlite.bz2: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/8e8da7fca114e0273cb5f96fa7b7142b65a6f103e3c4e6a24a38fd39c185e178-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/ccaa77571e7e1d0b3db4a8b316490c65b8a82a41b7866510eae8bd48465ac8e6-updateinfo.xml.bz2: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/ccaa77571e7e1d0b3db4a8b316490c65b8a82a41b7866510eae8bd48465ac8e6-updateinfo.xml.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.92/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://74.50.120.123/cpanelsync/repos/CentOS/7/EA4/repodata/458ff0677e8f8e1e0a7c4ea53f4b0afe5fa722a7ae5280c8428e87994b3762f3-filelists.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://74.50.120.123/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/8cd8bc2d2fc918c315046b553e84ce4da0469b3a457957dc329556907e5d325d-filelists.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/55b543a7f6fca2b895fd95d9ad7a13b62415e8b18cab83c2a585f88d67478ac9-primary.sqlite.bz2: [Errno 12] Timeout on https://repo.extreme-ix.org/epel/7/x86_64/repodata/55b543a7f6fca2b895fd95d9ad7a13b62415e8b18cab83c2a585f88d67478ac9-primary.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/a067bd2d6eee62e34edb112c90a16f5f50edb0c8a92e94f083208049c8c73ef6-other.sqlite.bz2: [Errno 12] Timeout on https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/a067bd2d6eee62e34edb112c90a16f5f50edb0c8a92e94f083208049c8c73ef6-other.sqlite.bz2: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/8e8da7fca114e0273cb5f96fa7b7142b65a6f103e3c4e6a24a38fd39c185e178-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/.

http://mirror.radoreservers.com/centos/7.9.2009/updates/x86_64/repodata/bc8950506fb13622afd9eb93c811884b6e2e7570afd5fac946f708ac01ae0cff-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.radoreservers.com/centos/7.9.2009/updates/x86_64/repodata/bc8950506fb13622afd9eb93c811884b6e2e7570afd5fac946f708ac01ae0cff-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://epel.mirror.angkasa.id/pub/epel/7/x86_64/repodata/ccaa77571e7e1d0b3db4a8b316490c65b8a82a41b7866510eae8bd48465ac8e6-updateinfo.xml.bz2: [Errno 12] Timeout on http://epel.mirror.angkasa.id/pub/epel/7/x86_64/repodata/ccaa77571e7e1d0b3db4a8b316490c65b8a82a41b7866510eae8bd48465ac8e6-updateinfo.xml.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.15.48.49/cpanelsync/repos/CentOS/7/EA4/repodata/458ff0677e8f8e1e0a7c4ea53f4b0afe5fa722a7ae5280c8428e87994b3762f3-filelists.sqlite.bz2: [Errno 12] Timeout on http://103.15.48.49/cpanelsync/repos/CentOS/7/EA4/repodata/458ff0677e8f8e1e0a7c4ea53f4b0afe5fa722a7ae5280c8428e87994b3762f3-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://118.88.24.67/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno 12] Timeout on http://118.88.24.67/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://118.88.24.67/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/8cd8bc2d2fc918c315046b553e84ce4da0469b3a457957dc329556907e5d325d-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/ccaa77571e7e1d0b3db4a8b316490c65b8a82a41b7866510eae8bd48465ac8e6-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/8e8da7fca114e0273cb5f96fa7b7142b65a6f103e3c4e6a24a38fd39c185e178-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://118.88.24.67/cpanelsync/repos/CentOS/7/EA4/repodata/458ff0677e8f8e1e0a7c4ea53f4b0afe5fa722a7ae5280c8428e87994b3762f3-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/8e8da7fca114e0273cb5f96fa7b7142b65a6f103e3c4e6a24a38fd39c185e178-filelists.sqlite.bz2: [Errno 12] Timeout on https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/8e8da7fca114e0273cb5f96fa7b7142b65a6f103e3c4e6a24a38fd39c185e178-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://102.22.80.80/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno 12] Timeout on http://102.22.80.80/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.120.66.133/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/8e8da7fca114e0273cb5f96fa7b7142b65a6f103e3c4e6a24a38fd39c185e178-filelists.sqlite.bz2: [Errno 12] Timeout on http://mirror.earthlink.iq/epel/7/x86_64/repodata/8e8da7fca114e0273cb5f96fa7b7142b65a6f103e3c4e6a24a38fd39c185e178-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.252.152.1/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno 12] Timeout on http://103.252.152.1/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.94/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://45.234.92.141/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno 12] Timeout on http://45.234.92.141/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://203.174.85.202/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno 12] Timeout on http://203.174.85.202/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://185.125.185.32/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno 12] Timeout on http://185.125.185.32/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/8e8da7fca114e0273cb5f96fa7b7142b65a6f103e3c4e6a24a38fd39c185e178-filelists.sqlite.bz2: [Errno 12] Timeout on https://repo.extreme-ix.org/epel/7/x86_64/repodata/8e8da7fca114e0273cb5f96fa7b7142b65a6f103e3c4e6a24a38fd39c185e178-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror.lzu.edu.cn/epel/7/x86_64/repodata/8e8da7fca114e0273cb5f96fa7b7142b65a6f103e3c4e6a24a38fd39c185e178-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://103.101.161.235/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno 12] Timeout on http://103.101.161.235/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://201.159.169.169/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-03-17 02:28:57 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-17 02:28:58 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-17 02:28:58 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-17 02:28:58 (4151) [[32mINFO[0m] 
* 2023-03-17 02:28:58 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-17 02:28:58 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-17 02:28:58 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-17 02:28:59 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-17 02:28:59 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-17 02:28:59 (4182) [[32mINFO[0m] 
* 2023-03-17 02:28:59 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-17 02:28:59 (4151) [[32mINFO[0m] 
* 2023-03-17 02:32:20 (4165) [[32mINFO[0m] 
* 2023-03-17 02:32:20 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-17 02:32:20 (4182) [[32mINFO[0m] 
* 2023-03-17 02:32:20 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-17 02:32:20 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-17 02:32:20 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-17 02:32:20 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BdfpbBzV0s/ea_profile.json
* 2023-03-17 02:32:21 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/BdfpbBzV0s/ea_profile.json
* 2023-03-17 02:32:21 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-17 02:32:23 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-17 15:58:21 (3805) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-03-17 15:58:21 (3806) [[31mERROR[0m] http://mirror.netdirekt.com.tr/centos/7.9.2009/updates/x86_64/repodata/bc8950506fb13622afd9eb93c811884b6e2e7570afd5fac946f708ac01ae0cff-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.netdirekt.com.tr/centos/7.9.2009/updates/x86_64/repodata/bc8950506fb13622afd9eb93c811884b6e2e7570afd5fac946f708ac01ae0cff-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
* 2023-03-17 15:58:21 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-17 15:58:22 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-17 15:58:22 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-17 15:58:22 (4151) [[32mINFO[0m] 
* 2023-03-17 15:58:22 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-17 15:58:22 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-17 15:58:22 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-17 15:58:23 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-17 15:58:23 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-17 15:58:23 (4182) [[32mINFO[0m] 
* 2023-03-17 15:58:23 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-17 15:58:23 (4151) [[32mINFO[0m] 
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/cpanel-plugins-c7-x86_64-mirrorlist error was
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m] 14: curl#52 - "Empty reply from server"
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m] 
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m] 
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m] 
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m] 
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m] 
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m] 
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m] 
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]         or
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m] 
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]         compromise:
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m] 
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m] 
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m] Cannot find a valid baseurl for repo: cpanel-plugins/x86_64
* 2023-03-17 15:58:42 (4182) [[32mINFO[0m] 
* 2023-03-17 15:58:42 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-17 15:58:42 (3661) [[32mINFO[0m] Checking /scripts/sysup
* 2023-03-17 15:58:42 (4150) [[32mINFO[0m] Running: /scripts/sysup
* 2023-03-17 15:58:42 (4151) [[32mINFO[0m] 
* 2023-03-17 15:58:42 (4165) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-03-17 15:58:44 (4165) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-03-17 15:58:44 (4182) [[32mINFO[0m] 
* 2023-03-17 15:58:44 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-17 15:58:44 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ArjPAL3XZq/ea_profile.json
* 2023-03-17 16:01:51 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/ArjPAL3XZq/ea_profile.json
* 2023-03-17 16:01:51 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-17 16:01:53 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-18 02:20:13 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-18 02:20:13 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-18 02:20:13 (4151) [[32mINFO[0m] 
* 2023-03-18 02:20:14 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-18 02:20:14 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-18 02:20:14 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-18 02:20:14 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-18 02:20:14 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-18 02:20:14 (4182) [[32mINFO[0m] 
* 2023-03-18 02:20:14 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-18 02:20:14 (4151) [[32mINFO[0m] 
* 2023-03-18 02:20:49 (4165) [[32mINFO[0m] 
* 2023-03-18 02:20:49 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-18 02:20:49 (4182) [[32mINFO[0m] 
* 2023-03-18 02:20:49 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-18 02:20:49 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-18 02:20:49 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-18 02:20:49 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/caOIBV2bUy/ea_profile.json
* 2023-03-18 02:20:50 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/caOIBV2bUy/ea_profile.json
* 2023-03-18 02:20:50 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-18 02:20:52 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-19 02:24:28 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-03-19 02:24:49 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-19 02:24:49 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-19 02:24:49 (4151) [[32mINFO[0m] 
* 2023-03-19 02:24:49 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-19 02:24:49 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-19 02:24:49 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-19 02:24:49 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-19 02:24:49 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-19 02:24:49 (4182) [[32mINFO[0m] 
* 2023-03-19 02:24:49 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-19 02:24:49 (4151) [[32mINFO[0m] 
* 2023-03-19 02:26:08 (4165) [[32mINFO[0m] 
* 2023-03-19 02:26:08 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-19 02:26:08 (4182) [[32mINFO[0m] 
* 2023-03-19 02:26:08 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-19 02:26:08 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-19 02:26:08 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-19 02:26:08 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rOjq83iNZ7/ea_profile.json
* 2023-03-19 02:26:10 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/rOjq83iNZ7/ea_profile.json
* 2023-03-19 02:26:10 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-19 02:26:12 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-20 02:20:43 (3805) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-03-20 02:20:43 (3806) [[31mERROR[0m] http://27.50.85.8/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno 12] Timeout on http://27.50.85.8/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.94/cpanelsync/repos/CentOS/7/EA4/repodata/309f8b71a6ed09e3d2d68c9399903ede88f12b6f5a75c72f46e885b27431a8bc-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-03-20 02:20:43 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-20 02:20:43 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-20 02:20:43 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-20 02:20:43 (4151) [[32mINFO[0m] 
* 2023-03-20 02:20:44 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-20 02:20:44 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-20 02:20:44 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-20 02:20:44 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-20 02:20:44 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-20 02:20:44 (4182) [[32mINFO[0m] 
* 2023-03-20 02:20:44 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-20 02:20:44 (4151) [[32mINFO[0m] 
* 2023-03-20 02:22:17 (4165) [[32mINFO[0m] http://mirror.radoreservers.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.radoreservers.com/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-03-20 02:22:17 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-03-20 02:22:33 (4165) [[32mINFO[0m] 
* 2023-03-20 02:22:33 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-20 02:22:33 (4182) [[32mINFO[0m] 
* 2023-03-20 02:22:33 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-20 02:22:33 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-20 02:22:33 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-20 02:22:33 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hXQD0wvFyO/ea_profile.json
* 2023-03-20 02:22:35 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/hXQD0wvFyO/ea_profile.json
* 2023-03-20 02:22:35 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-20 02:22:36 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-21 02:21:19 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-03-21 02:21:49 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-21 02:21:49 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-21 02:21:49 (4151) [[32mINFO[0m] 
* 2023-03-21 02:21:50 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-21 02:21:50 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-21 02:21:50 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-21 02:21:50 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-21 02:21:50 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-21 02:21:50 (4182) [[32mINFO[0m] 
* 2023-03-21 02:21:50 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-21 02:21:50 (4151) [[32mINFO[0m] 
* 2023-03-21 02:22:26 (4165) [[32mINFO[0m] 
* 2023-03-21 02:22:26 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-21 02:22:26 (4182) [[32mINFO[0m] 
* 2023-03-21 02:22:26 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-21 02:22:26 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-21 02:22:26 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-21 02:22:26 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BBg8QNKzjV/ea_profile.json
* 2023-03-21 02:22:28 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/BBg8QNKzjV/ea_profile.json
* 2023-03-21 02:22:28 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-21 02:22:29 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-22 02:19:05 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-03-22 02:21:30 (3805) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-03-22 02:21:30 (3806) [[31mERROR[0m] http://mirrors.isu.net.sa/centos/7.9.2009/updates/x86_64/repodata/1117ab2561f3d54eccdd8b8d6c0d9507082d4cf7e09c79d25f5a68b9b629a5a5-primary.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/.

http://centos.telecoms.bg/7.9.2009/updates/x86_64/repodata/1117ab2561f3d54eccdd8b8d6c0d9507082d4cf7e09c79d25f5a68b9b629a5a5-primary.sqlite.bz2: [Errno 12] Timeout on http://centos.telecoms.bg/7.9.2009/updates/x86_64/repodata/1117ab2561f3d54eccdd8b8d6c0d9507082d4cf7e09c79d25f5a68b9b629a5a5-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
* 2023-03-22 02:21:30 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-22 02:21:30 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-22 02:21:30 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-22 02:21:30 (4151) [[32mINFO[0m] 
* 2023-03-22 02:21:30 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-22 02:21:31 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-22 02:21:31 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-22 02:21:31 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-22 02:21:31 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-22 02:21:31 (4182) [[32mINFO[0m] 
* 2023-03-22 02:21:31 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-22 02:21:31 (4151) [[32mINFO[0m] 
* 2023-03-22 02:22:01 (4165) [[32mINFO[0m] 
* 2023-03-22 02:22:01 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-22 02:22:01 (4182) [[32mINFO[0m] 
* 2023-03-22 02:22:01 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-22 02:22:01 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-22 02:22:01 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-22 02:22:01 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VeMtH_24Zg/ea_profile.json
* 2023-03-22 02:22:02 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/VeMtH_24Zg/ea_profile.json
* 2023-03-22 02:22:02 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-22 02:22:04 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-23 02:23:33 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-03-23 02:23:47 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-23 02:23:47 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-23 02:23:47 (4151) [[32mINFO[0m] 
* 2023-03-23 02:23:47 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-23 02:23:47 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-23 02:23:47 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-23 02:23:48 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-23 02:23:48 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-23 02:23:48 (4182) [[32mINFO[0m] 
* 2023-03-23 02:23:48 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-23 02:23:48 (4151) [[32mINFO[0m] 
* 2023-03-23 02:24:15 (4165) [[32mINFO[0m] 
* 2023-03-23 02:24:15 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-23 02:24:15 (4182) [[32mINFO[0m] 
* 2023-03-23 02:24:15 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-23 02:24:15 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-23 02:24:15 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-23 02:24:15 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uZK9TjstQh/ea_profile.json
* 2023-03-23 02:24:17 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/uZK9TjstQh/ea_profile.json
* 2023-03-23 02:24:17 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-23 02:24:19 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-24 02:16:08 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-03-24 02:16:41 (3805) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-03-24 02:16:41 (3806) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-03-24 02:16:41 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-24 02:16:41 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-24 02:16:41 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-24 02:16:41 (4151) [[32mINFO[0m] 
* 2023-03-24 02:16:41 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-24 02:16:41 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-24 02:16:41 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-24 02:16:42 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-24 02:16:42 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-24 02:16:42 (4182) [[32mINFO[0m] 
* 2023-03-24 02:16:42 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-24 02:16:42 (4151) [[32mINFO[0m] 
* 2023-03-24 02:17:10 (4165) [[32mINFO[0m] http://208.100.0.204/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/56e4cec14ddc64fea857cad1ff453c4cfc6743e85a28acade985715880bd6eb1-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
* 2023-03-24 02:17:10 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-03-24 02:17:10 (4165) [[32mINFO[0m] http://208.100.0.204/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
* 2023-03-24 02:17:10 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-03-24 02:17:38 (4165) [[32mINFO[0m] http://mirror.centos.jt.iq/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.centos.jt.iq/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-03-24 02:17:38 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-03-24 02:17:46 (4165) [[32mINFO[0m] http://118.88.24.67/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno 12] Timeout on http://118.88.24.67/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-03-24 02:17:46 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-03-24 02:17:47 (4165) [[32mINFO[0m] http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: [Errno 12] Timeout on http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-03-24 02:17:47 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-03-24 02:17:48 (4165) [[32mINFO[0m] http://184.94.196.93/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-03-24 02:17:48 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-03-24 02:18:23 (4165) [[32mINFO[0m] http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-03-24 02:18:23 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-03-24 02:18:25 (4165) [[32mINFO[0m] http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-03-24 02:18:25 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-03-24 02:18:42 (4165) [[32mINFO[0m] 
* 2023-03-24 02:18:42 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-24 02:18:42 (4182) [[32mINFO[0m] 
* 2023-03-24 02:18:42 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-24 02:18:42 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-24 02:18:42 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-24 02:18:42 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EpTlPH_x6T/ea_profile.json
* 2023-03-24 02:18:43 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/EpTlPH_x6T/ea_profile.json
* 2023-03-24 02:18:43 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-24 02:18:45 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-24 15:56:39 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-03-24 16:01:22 (3805) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-03-24 16:01:22 (3806) [[31mERROR[0m] http://102.22.80.80/cpanelsync/repos/CentOS/7/EA4/repodata/repomd.xml: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://103.48.119.120/cpanelsync/repos/CentOS/7/EA4/repodata/repomd.xml: [Errno 12] Timeout on http://103.48.119.120/cpanelsync/repos/CentOS/7/EA4/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.101.161.235/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://103.101.161.235/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/f13540658ea44250459f7b238a31050f36b0d7823889110c2da3e2ecb38dfd1d-prestodelta.xml.gz: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/f13540658ea44250459f7b238a31050f36b0d7823889110c2da3e2ecb38dfd1d-prestodelta.xml.gz: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')
Trying other mirror.
http://203.174.85.202/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/a168648430654a927dcc94a55c38cf2253df920819831ba8a746fe09d0907684-other.sqlite.bz2: [Errno 12] Timeout on http://203.174.85.202/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/a168648430654a927dcc94a55c38cf2253df920819831ba8a746fe09d0907684-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirror.netdirekt.com.tr/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.netdirekt.com.tr/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.
http://63.247.64.58/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/a168648430654a927dcc94a55c38cf2253df920819831ba8a746fe09d0907684-other.sqlite.bz2: [Errno 12] Timeout on http://63.247.64.58/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/a168648430654a927dcc94a55c38cf2253df920819831ba8a746fe09d0907684-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirror.netdirekt.com.tr/centos/7.9.2009/extras/x86_64/repodata/78c0e5530bc46d128e18eca9ff16b2d0651efdb33434408f8ff1db4d14f1bb99-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.netdirekt.com.tr/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.
http://103.252.152.1/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/a168648430654a927dcc94a55c38cf2253df920819831ba8a746fe09d0907684-other.sqlite.bz2: [Errno 12] Timeout on http://103.252.152.1/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/a168648430654a927dcc94a55c38cf2253df920819831ba8a746fe09d0907684-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://45.234.92.141/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/a168648430654a927dcc94a55c38cf2253df920819831ba8a746fe09d0907684-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://185.157.208.252/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/a168648430654a927dcc94a55c38cf2253df920819831ba8a746fe09d0907684-other.sqlite.bz2: [Errno 12] Timeout on http://185.157.208.252/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/a168648430654a927dcc94a55c38cf2253df920819831ba8a746fe09d0907684-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://185.125.185.32/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/a168648430654a927dcc94a55c38cf2253df920819831ba8a746fe09d0907684-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://74.50.120.123/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/a168648430654a927dcc94a55c38cf2253df920819831ba8a746fe09d0907684-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://184.94.196.94/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/a168648430654a927dcc94a55c38cf2253df920819831ba8a746fe09d0907684-other.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.94/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/a168648430654a927dcc94a55c38cf2253df920819831ba8a746fe09d0907684-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://201.159.169.169/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/a168648430654a927dcc94a55c38cf2253df920819831ba8a746fe09d0907684-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-03-24 16:01:22 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-24 16:01:22 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-24 16:01:22 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-24 16:01:22 (4151) [[32mINFO[0m] 
* 2023-03-24 16:01:22 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-24 16:01:23 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-24 16:01:23 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-24 16:01:23 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-24 16:01:23 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-24 16:01:23 (4182) [[32mINFO[0m] 
* 2023-03-24 16:01:23 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-24 16:01:23 (4151) [[32mINFO[0m] 
* 2023-03-24 16:01:55 (4165) [[32mINFO[0m] 
* 2023-03-24 16:01:55 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-24 16:01:56 (4182) [[32mINFO[0m] 
* 2023-03-24 16:01:56 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-24 16:01:56 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-24 16:01:56 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-24 16:01:56 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/k9Bddj_UCd/ea_profile.json
* 2023-03-24 16:01:57 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/k9Bddj_UCd/ea_profile.json
* 2023-03-24 16:01:57 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-24 16:01:59 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-25 02:17:53 (3805) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-03-25 02:17:53 (3806) [[31mERROR[0m] http://203.174.85.202/cpanelsync/repos/CentOS/7/EA4/repodata/4dc275b1065ab1fa610923a978d15fd7e96276ef860175131d7f8c5f5de92411-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://centos.vargonen.com/centos/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
Trying other mirror.
http://201.159.169.169/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: [Errno 12] Timeout on http://201.159.169.169/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://201.159.169.169/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno 12] Timeout on http://201.159.169.169/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirror.netdirekt.com.tr/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on http://mirror.netdirekt.com.tr/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirror.alastyr.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.alastyr.com/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')
Trying other mirror.
http://74.50.120.123/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://kozyatagi.mirror.guzel.net.tr/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 12] Timeout on http://kozyatagi.mirror.guzel.net.tr/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://45.234.92.141/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno 12] Timeout on http://45.234.92.141/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://27.50.85.8/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://45.234.92.141/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: [Errno 12] Timeout on http://45.234.92.141/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-03-25 02:17:53 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-25 02:17:54 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-25 02:17:54 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-25 02:17:54 (4151) [[32mINFO[0m] 
* 2023-03-25 02:17:54 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-25 02:17:54 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-25 02:17:54 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-25 02:17:54 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-25 02:17:54 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-25 02:17:54 (4182) [[32mINFO[0m] 
* 2023-03-25 02:17:54 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-25 02:17:54 (4151) [[32mINFO[0m] 
* 2023-03-25 02:18:29 (4165) [[32mINFO[0m] 
* 2023-03-25 02:18:29 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-25 02:18:29 (4182) [[32mINFO[0m] 
* 2023-03-25 02:18:29 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-25 02:18:29 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-25 02:18:29 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-25 02:18:29 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/R89RgRowGp/ea_profile.json
* 2023-03-25 02:18:30 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/R89RgRowGp/ea_profile.json
* 2023-03-25 02:18:30 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-25 02:18:32 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-25 10:54:42 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-25 10:54:42 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-25 10:54:42 (4151) [[32mINFO[0m] 
* 2023-03-25 10:54:42 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-25 10:54:42 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-25 10:54:42 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-25 10:54:44 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-25 10:54:44 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-25 10:54:44 (4182) [[32mINFO[0m] 
* 2023-03-25 10:54:44 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-25 10:54:44 (4151) [[32mINFO[0m] 
* 2023-03-25 10:56:11 (4165) [[32mINFO[0m] 
* 2023-03-25 10:56:11 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-25 10:56:11 (4182) [[32mINFO[0m] 
* 2023-03-25 10:56:11 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-25 10:56:11 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-25 10:56:11 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-25 10:56:11 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BZODxaFZ09/ea_profile.json
* 2023-03-25 10:56:12 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/BZODxaFZ09/ea_profile.json
* 2023-03-25 10:56:12 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-25 10:56:14 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-25 11:34:47 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-03-25 11:38:10 (3805) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-03-25 11:38:10 (3806) [[31mERROR[0m] http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/4dc275b1065ab1fa610923a978d15fd7e96276ef860175131d7f8c5f5de92411-other.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/4dc275b1065ab1fa610923a978d15fd7e96276ef860175131d7f8c5f5de92411-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://118.88.24.67/cpanelsync/repos/CentOS/7/EA4/repodata/4dc275b1065ab1fa610923a978d15fd7e96276ef860175131d7f8c5f5de92411-other.sqlite.bz2: [Errno 12] Timeout on http://118.88.24.67/cpanelsync/repos/CentOS/7/EA4/repodata/4dc275b1065ab1fa610923a978d15fd7e96276ef860175131d7f8c5f5de92411-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/4dc275b1065ab1fa610923a978d15fd7e96276ef860175131d7f8c5f5de92411-other.sqlite.bz2: [Errno 12] Timeout on http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/4dc275b1065ab1fa610923a978d15fd7e96276ef860175131d7f8c5f5de92411-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://102.22.80.80/cpanelsync/repos/CentOS/7/EA4/repodata/4dc275b1065ab1fa610923a978d15fd7e96276ef860175131d7f8c5f5de92411-other.sqlite.bz2: [Errno 12] Timeout on http://102.22.80.80/cpanelsync/repos/CentOS/7/EA4/repodata/4dc275b1065ab1fa610923a978d15fd7e96276ef860175131d7f8c5f5de92411-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://74.50.120.123/cpanelsync/repos/CentOS/7/EA4/repodata/4dc275b1065ab1fa610923a978d15fd7e96276ef860175131d7f8c5f5de92411-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-03-25 11:38:10 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-25 11:38:10 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-25 11:38:10 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-25 11:38:10 (4151) [[32mINFO[0m] 
* 2023-03-25 11:38:11 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-25 11:38:11 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-25 11:38:11 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-25 11:38:11 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-25 11:38:11 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-25 11:38:11 (4182) [[32mINFO[0m] 
* 2023-03-25 11:38:11 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-25 11:38:11 (4151) [[32mINFO[0m] 
* 2023-03-25 11:39:53 (4165) [[32mINFO[0m] http://istanbul.centos-mirror.guzel.net.tr/7.9.2009/updates/x86_64/repodata/1117ab2561f3d54eccdd8b8d6c0d9507082d4cf7e09c79d25f5a68b9b629a5a5-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-03-25 11:39:53 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-03-25 11:40:08 (4165) [[32mINFO[0m] 
* 2023-03-25 11:40:08 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-25 11:40:08 (4182) [[32mINFO[0m] 
* 2023-03-25 11:40:08 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-25 11:40:08 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-25 11:40:08 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-25 11:40:08 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nRSjiQB_oF/ea_profile.json
* 2023-03-25 11:40:09 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/nRSjiQB_oF/ea_profile.json
* 2023-03-25 11:40:09 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-25 11:40:11 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-26 02:19:10 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-26 02:19:10 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-26 02:19:10 (4151) [[32mINFO[0m] 
* 2023-03-26 02:19:10 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-26 02:19:10 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-26 02:19:10 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-26 02:19:11 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-26 02:19:11 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-26 02:19:11 (4182) [[32mINFO[0m] 
* 2023-03-26 02:19:11 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-26 02:19:11 (4151) [[32mINFO[0m] 
* 2023-03-26 02:19:50 (4165) [[32mINFO[0m] 
* 2023-03-26 02:19:50 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-26 02:19:51 (4182) [[32mINFO[0m] 
* 2023-03-26 02:19:51 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-26 02:19:51 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-26 02:19:51 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-26 02:19:51 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PPpmem5Bnz/ea_profile.json
* 2023-03-26 02:19:52 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/PPpmem5Bnz/ea_profile.json
* 2023-03-26 02:19:52 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-26 02:19:54 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-27 02:15:24 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-27 02:15:24 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-27 02:15:24 (4151) [[32mINFO[0m] 
* 2023-03-27 02:15:24 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-27 02:15:24 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-27 02:15:24 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-27 02:15:24 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-27 02:15:24 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-27 02:15:24 (4182) [[32mINFO[0m] 
* 2023-03-27 02:15:24 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-27 02:15:24 (4151) [[32mINFO[0m] 
* 2023-03-27 02:15:56 (4165) [[32mINFO[0m] http://mirror.bursabil.com.tr/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2a04:3880:0:16::205: Network is unreachable"
* 2023-03-27 02:15:56 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-03-27 02:16:04 (4165) [[32mINFO[0m] http://mirror.bursabil.com.tr/centos/7.9.2009/updates/x86_64/repodata/1117ab2561f3d54eccdd8b8d6c0d9507082d4cf7e09c79d25f5a68b9b629a5a5-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2a04:3880:0:16::205: Network is unreachable"
* 2023-03-27 02:16:04 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-03-27 02:17:24 (4165) [[32mINFO[0m] 
* 2023-03-27 02:17:24 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-27 02:17:25 (4182) [[32mINFO[0m] 
* 2023-03-27 02:17:25 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-27 02:17:25 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-27 02:17:25 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-27 02:17:28 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/h85wI9ZKyl/ea_profile.json
* 2023-03-27 02:17:29 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/h85wI9ZKyl/ea_profile.json
* 2023-03-27 02:17:29 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-27 02:17:31 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-28 02:31:41 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-03-28 02:31:57 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-28 02:31:57 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-28 02:31:57 (4151) [[32mINFO[0m] 
* 2023-03-28 02:31:58 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-28 02:31:58 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-28 02:31:58 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-28 02:31:58 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-28 02:31:58 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-28 02:31:58 (4182) [[32mINFO[0m] 
* 2023-03-28 02:31:58 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-28 02:31:58 (4151) [[32mINFO[0m] 
* 2023-03-28 02:32:27 (4165) [[32mINFO[0m] http://mirror.bursabil.com.tr/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2a04:3880:0:16::205: Network is unreachable"
* 2023-03-28 02:32:27 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-03-28 02:32:46 (4165) [[32mINFO[0m] http://mirror.bursabil.com.tr/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.bursabil.com.tr/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-03-28 02:32:46 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-03-28 02:33:06 (4165) [[32mINFO[0m] 
* 2023-03-28 02:33:06 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-28 02:33:06 (4182) [[32mINFO[0m] 
* 2023-03-28 02:33:06 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-28 02:33:06 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-28 02:33:06 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-28 02:33:06 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/swaESTJi_q/ea_profile.json
* 2023-03-28 02:33:07 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/swaESTJi_q/ea_profile.json
* 2023-03-28 02:33:07 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-28 02:33:09 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-29 02:20:57 (3805) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-03-29 02:20:57 (3806) [[31mERROR[0m] http://74.50.120.123/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://74.50.120.123/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno 12] Timeout on http://74.50.120.123/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/2762f5c8a7bede2413dd1dca4cf5837b2e5f4a3aa7d4f3174710bf4c18ca5e08-prestodelta.xml.gz: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/2762f5c8a7bede2413dd1dca4cf5837b2e5f4a3aa7d4f3174710bf4c18ca5e08-prestodelta.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirror.radoreservers.com/centos/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on http://mirror.radoreservers.com/centos/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.93/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.92/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://mirror.radoreservers.com/centos/7.9.2009/updates/x86_64/repodata/1117ab2561f3d54eccdd8b8d6c0d9507082d4cf7e09c79d25f5a68b9b629a5a5-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.radoreservers.com/centos/7.9.2009/updates/x86_64/repodata/1117ab2561f3d54eccdd8b8d6c0d9507082d4cf7e09c79d25f5a68b9b629a5a5-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://27.50.85.8/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: [Errno 12] Timeout on http://27.50.85.8/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://63.247.64.58/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: [Errno 12] Timeout on http://63.247.64.58/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: [Errno 12] Timeout on http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://45.228.65.220/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: [Errno 12] Timeout on http://45.228.65.220/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.94/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://208.74.123.61/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://185.15.22.168/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: [Errno 12] Timeout on http://185.15.22.168/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/bea6995bab48bb1dbd1571a0e70cbfa2377931c2cbecb48d40a4b23897d6c6e1-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-03-29 02:20:57 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-29 02:20:57 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-29 02:20:57 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-29 02:20:57 (4151) [[32mINFO[0m] 
* 2023-03-29 02:20:58 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-29 02:20:58 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-29 02:20:58 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-29 02:20:58 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-29 02:20:58 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-29 02:20:58 (4182) [[32mINFO[0m] 
* 2023-03-29 02:20:58 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-29 02:20:58 (4151) [[32mINFO[0m] 
* 2023-03-29 02:21:33 (4165) [[32mINFO[0m] 
* 2023-03-29 02:21:33 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-29 02:21:33 (4182) [[32mINFO[0m] 
* 2023-03-29 02:21:33 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-29 02:21:33 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-29 02:21:33 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-29 02:21:34 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HC4SQeCkef/ea_profile.json
* 2023-03-29 02:21:36 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/HC4SQeCkef/ea_profile.json
* 2023-03-29 02:21:36 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-29 02:21:37 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-30 02:21:57 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-03-30 02:22:35 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-30 02:22:35 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-30 02:22:35 (4151) [[32mINFO[0m] 
* 2023-03-30 02:22:35 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-30 02:22:35 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-30 02:22:35 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-30 02:22:35 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-30 02:22:35 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-30 02:22:35 (4182) [[32mINFO[0m] 
* 2023-03-30 02:22:35 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-30 02:22:35 (4151) [[32mINFO[0m] 
* 2023-03-30 02:23:15 (4165) [[32mINFO[0m] 
* 2023-03-30 02:23:15 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-30 02:23:15 (4182) [[32mINFO[0m] 
* 2023-03-30 02:23:15 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-30 02:23:15 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-30 02:23:15 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-30 02:23:15 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/d9pvn6C8Mn/ea_profile.json
* 2023-03-30 02:23:17 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/d9pvn6C8Mn/ea_profile.json
* 2023-03-30 02:23:17 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-30 02:23:18 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-31 02:20:09 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-03-31 02:20:26 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-31 02:20:26 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-31 02:20:26 (4151) [[32mINFO[0m] 
* 2023-03-31 02:20:27 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-31 02:20:27 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-31 02:20:27 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-31 02:20:27 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-31 02:20:27 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-31 02:20:27 (4182) [[32mINFO[0m] 
* 2023-03-31 02:20:27 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-31 02:20:27 (4151) [[32mINFO[0m] 
* 2023-03-31 02:21:14 (4165) [[32mINFO[0m] 
* 2023-03-31 02:21:14 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-31 02:21:14 (4182) [[32mINFO[0m] 
* 2023-03-31 02:21:14 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-31 02:21:14 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-31 02:21:14 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-31 02:21:14 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FMJYx6uKpH/ea_profile.json
* 2023-03-31 02:21:15 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/FMJYx6uKpH/ea_profile.json
* 2023-03-31 02:21:16 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-31 02:21:18 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-03-31 15:54:11 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-03-31 16:02:27 (3805) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-03-31 16:02:27 (3806) [[31mERROR[0m] http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.92/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/fa0329c15a0e98050e96c821e3817c60ca83b0db6ced3367ac98175763e9238f-other.sqlite.bz2: [Errno 12] Timeout on https://mirrors.thzhost.com/epel/7/x86_64/repodata/fa0329c15a0e98050e96c821e3817c60ca83b0db6ced3367ac98175763e9238f-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror.sabay.com.kh/epel/7/x86_64/repodata/fa0329c15a0e98050e96c821e3817c60ca83b0db6ced3367ac98175763e9238f-other.sqlite.bz2: [Errno 12] Timeout on https://mirror.sabay.com.kh/epel/7/x86_64/repodata/fa0329c15a0e98050e96c821e3817c60ca83b0db6ced3367ac98175763e9238f-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: [Errno 12] Timeout on http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/fa0329c15a0e98050e96c821e3817c60ca83b0db6ced3367ac98175763e9238f-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.earthlink.iq/epel/7/x86_64/repodata/fa0329c15a0e98050e96c821e3817c60ca83b0db6ced3367ac98175763e9238f-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://185.157.208.252/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: [Errno 12] Timeout on http://185.157.208.252/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/fa0329c15a0e98050e96c821e3817c60ca83b0db6ced3367ac98175763e9238f-other.sqlite.bz2: [Errno 12] Timeout on https://repo.extreme-ix.org/epel/7/x86_64/repodata/fa0329c15a0e98050e96c821e3817c60ca83b0db6ced3367ac98175763e9238f-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.17.8.8/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: [Errno 12] Timeout on http://103.17.8.8/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://epel.mirror.angkasa.id/pub/epel/7/x86_64/repodata/fa0329c15a0e98050e96c821e3817c60ca83b0db6ced3367ac98175763e9238f-other.sqlite.bz2: [Errno 12] Timeout on http://epel.mirror.angkasa.id/pub/epel/7/x86_64/repodata/fa0329c15a0e98050e96c821e3817c60ca83b0db6ced3367ac98175763e9238f-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.15.48.49/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: [Errno 12] Timeout on http://103.15.48.49/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://118.88.24.67/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: [Errno 12] Timeout on http://118.88.24.67/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.120.66.133/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/fa0329c15a0e98050e96c821e3817c60ca83b0db6ced3367ac98175763e9238f-other.sqlite.bz2: [Errno 12] Timeout on https://mirrors.thzhost.com/epel/7/x86_64/repodata/fa0329c15a0e98050e96c821e3817c60ca83b0db6ced3367ac98175763e9238f-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror.sabay.com.kh/epel/7/x86_64/repodata/fa0329c15a0e98050e96c821e3817c60ca83b0db6ced3367ac98175763e9238f-other.sqlite.bz2: [Errno 12] Timeout on https://mirror.sabay.com.kh/epel/7/x86_64/repodata/fa0329c15a0e98050e96c821e3817c60ca83b0db6ced3367ac98175763e9238f-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
* 2023-03-31 16:02:27 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-31 16:02:27 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-03-31 16:02:27 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-03-31 16:02:27 (4151) [[32mINFO[0m] 
* 2023-03-31 16:02:28 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-31 16:02:28 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-03-31 16:02:28 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-03-31 16:02:28 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-03-31 16:02:28 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-03-31 16:02:28 (4182) [[32mINFO[0m] 
* 2023-03-31 16:02:28 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-03-31 16:02:28 (4151) [[32mINFO[0m] 
* 2023-03-31 16:02:42 (4165) [[32mINFO[0m] http://mirror.earthlink.iq/epel/7/x86_64/repodata/97d2e9722dd5c0662a5c885a746a127e951f8860139076802e27d35eadb4aa45-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 500 - Internal Server Error
* 2023-03-31 16:02:42 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-03-31 16:02:42 (4165) [[32mINFO[0m] http://mirror.earthlink.iq/epel/7/x86_64/repodata/9be05b953087c9db75469093587be413b2d7d3c565361fcf5aefbbf7f3e0aa55-updateinfo.xml.bz2: [Errno 14] HTTP Error 500 - Internal Server Error
* 2023-03-31 16:02:42 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-03-31 16:03:31 (4165) [[32mINFO[0m] 
* 2023-03-31 16:03:31 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-31 16:03:31 (4182) [[32mINFO[0m] 
* 2023-03-31 16:03:31 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-31 16:03:31 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-31 16:03:31 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-31 16:03:35 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3I8quB30Cu/ea_profile.json
* 2023-03-31 16:03:37 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/3I8quB30Cu/ea_profile.json
* 2023-03-31 16:03:37 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-03-31 16:03:38 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-01 02:22:46 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-04-01 02:23:02 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-01 02:23:02 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-01 02:23:02 (4151) [[32mINFO[0m] 
* 2023-04-01 02:23:02 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-01 02:23:02 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-01 02:23:02 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-04-01 02:23:03 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-01 02:23:03 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-01 02:23:03 (4182) [[32mINFO[0m] 
* 2023-04-01 02:23:03 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-01 02:23:03 (4151) [[32mINFO[0m] 
* 2023-04-01 02:24:03 (4165) [[32mINFO[0m] 
* 2023-04-01 02:24:03 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-01 02:24:03 (4182) [[32mINFO[0m] 
* 2023-04-01 02:24:03 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-01 02:24:03 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-01 02:24:03 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-01 02:24:03 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QnW_gB0T_s/ea_profile.json
* 2023-04-01 02:24:04 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/QnW_gB0T_s/ea_profile.json
* 2023-04-01 02:24:04 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-01 02:24:06 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-02 02:23:15 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-04-02 02:23:34 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-02 02:23:34 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-02 02:23:34 (4151) [[32mINFO[0m] 
* 2023-04-02 02:23:34 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-02 02:23:35 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-02 02:23:35 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-04-02 02:23:35 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-02 02:23:35 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-02 02:23:35 (4182) [[32mINFO[0m] 
* 2023-04-02 02:23:35 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-02 02:23:35 (4151) [[32mINFO[0m] 
* 2023-04-02 02:29:37 (4165) [[32mINFO[0m] 
* 2023-04-02 02:29:37 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-02 02:29:37 (4182) [[32mINFO[0m] 
* 2023-04-02 02:29:37 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-02 02:29:37 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-02 02:29:37 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-02 02:29:40 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BIpf7GV0pL/ea_profile.json
* 2023-04-02 02:29:42 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/BIpf7GV0pL/ea_profile.json
* 2023-04-02 02:29:42 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-02 02:29:43 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-03 02:20:46 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-04-03 02:21:08 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-03 02:21:08 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-03 02:21:08 (4151) [[32mINFO[0m] 
* 2023-04-03 02:21:09 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-03 02:21:09 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-03 02:21:09 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-04-03 02:21:09 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-03 02:21:09 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-03 02:21:09 (4182) [[32mINFO[0m] 
* 2023-04-03 02:21:09 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-03 02:21:09 (4151) [[32mINFO[0m] 
* 2023-04-03 02:22:00 (4165) [[32mINFO[0m] 
* 2023-04-03 02:22:00 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-03 02:22:00 (4182) [[32mINFO[0m] 
* 2023-04-03 02:22:00 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-03 02:22:00 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-03 02:22:00 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-03 02:22:00 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/V9pXjCetZM/ea_profile.json
* 2023-04-03 02:22:02 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/V9pXjCetZM/ea_profile.json
* 2023-04-03 02:22:02 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-03 02:22:04 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-04 02:18:25 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-04-04 02:19:24 (3805) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-04-04 02:19:24 (3806) [[31mERROR[0m] http://centos.spd.co.il/7.9.2009/updates/x86_64/repodata/f561ac4dfb872c0e3239724bd06bfd9f555fdf8ad5482367d25440ffed97b095-other.sqlite.bz2: [Errno 14] HTTP Error 403 - Forbidden
Trying other mirror.
To address this issue please refer to the below wiki article

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

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

http://centos.activecloud.co.il/7.9.2009/updates/x86_64/repodata/f561ac4dfb872c0e3239724bd06bfd9f555fdf8ad5482367d25440ffed97b095-other.sqlite.bz2: [Errno 14] HTTP Error 403 - Forbidden
Trying other mirror.
* 2023-04-04 02:19:24 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-04 02:19:25 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-04 02:19:25 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-04 02:19:25 (4151) [[32mINFO[0m] 
* 2023-04-04 02:19:25 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-04 02:19:25 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-04 02:19:25 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-04-04 02:19:26 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-04 02:19:26 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-04 02:19:26 (4182) [[32mINFO[0m] 
* 2023-04-04 02:19:26 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-04 02:19:26 (4151) [[32mINFO[0m] 
* 2023-04-04 02:20:18 (4165) [[32mINFO[0m] 
* 2023-04-04 02:20:18 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-04 02:20:18 (4182) [[32mINFO[0m] 
* 2023-04-04 02:20:18 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-04 02:20:18 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-04 02:20:18 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-04 02:20:18 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TzXtQXUpd5/ea_profile.json
* 2023-04-04 02:20:19 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/TzXtQXUpd5/ea_profile.json
* 2023-04-04 02:20:19 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-04 02:20:21 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-05 02:18:54 (3805) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-04-05 02:18:54 (3806) [[31mERROR[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/97d2e9722dd5c0662a5c885a746a127e951f8860139076802e27d35eadb4aa45-comps-Everything.x86_64.xml.gz: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/97d2e9722dd5c0662a5c885a746a127e951f8860139076802e27d35eadb4aa45-comps-Everything.x86_64.xml.gz: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')
Trying other mirror.
http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/72742c4b0f894f6a176156d6158d8c522d63fa57efa19c69527445eba1a4e06a-filelists.sqlite.bz2: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/72742c4b0f894f6a176156d6158d8c522d63fa57efa19c69527445eba1a4e06a-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.92/cpanelsync/repos/CentOS/7/EA4/repodata/3fb64d074ab23c61ea7cf6a0e497efb6af75a1afc534221dd7e461e8eaab129c-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-04-05 02:18:54 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-05 02:18:54 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-05 02:18:54 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-05 02:18:54 (4151) [[32mINFO[0m] 
* 2023-04-05 02:18:55 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-05 02:18:55 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-05 02:18:55 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-04-05 02:18:55 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-05 02:18:55 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-05 02:18:55 (4182) [[32mINFO[0m] 
* 2023-04-05 02:18:55 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-05 02:18:55 (4151) [[32mINFO[0m] 
* 2023-04-05 02:19:25 (4165) [[32mINFO[0m] 
* 2023-04-05 02:19:25 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-05 02:19:25 (4182) [[32mINFO[0m] 
* 2023-04-05 02:19:25 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-05 02:19:25 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-05 02:19:25 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-05 02:19:25 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Y9a3Fbnuvo/ea_profile.json
* 2023-04-05 02:19:27 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/Y9a3Fbnuvo/ea_profile.json
* 2023-04-05 02:19:27 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-05 02:19:29 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-06 02:27:54 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-04-06 02:28:07 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-06 02:28:07 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-06 02:28:07 (4151) [[32mINFO[0m] 
* 2023-04-06 02:28:07 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-06 02:28:07 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-06 02:28:07 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-04-06 02:28:07 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-06 02:28:07 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-06 02:28:07 (4182) [[32mINFO[0m] 
* 2023-04-06 02:28:07 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-06 02:28:07 (4151) [[32mINFO[0m] 
* 2023-04-06 02:28:47 (4165) [[32mINFO[0m] 
* 2023-04-06 02:28:47 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-06 02:28:47 (4182) [[32mINFO[0m] 
* 2023-04-06 02:28:47 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-06 02:28:47 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-06 02:28:47 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-06 02:28:47 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lLKHwcevNJ/ea_profile.json
* 2023-04-06 02:28:49 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/lLKHwcevNJ/ea_profile.json
* 2023-04-06 02:28:49 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-06 02:28:51 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-07 02:19:20 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-04-07 02:19:49 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-07 02:19:49 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-07 02:19:49 (4151) [[32mINFO[0m] 
* 2023-04-07 02:19:49 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-07 02:19:49 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-07 02:19:50 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-04-07 02:19:50 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-07 02:19:50 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-07 02:19:50 (4182) [[32mINFO[0m] 
* 2023-04-07 02:19:50 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-07 02:19:50 (4151) [[32mINFO[0m] 
* 2023-04-07 02:21:12 (4165) [[32mINFO[0m] 
* 2023-04-07 02:21:12 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-07 02:21:12 (4182) [[32mINFO[0m] 
* 2023-04-07 02:21:12 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-07 02:21:12 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-07 02:21:12 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-07 02:21:12 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hsRSk_xIyt/ea_profile.json
* 2023-04-07 02:21:14 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/hsRSk_xIyt/ea_profile.json
* 2023-04-07 02:21:14 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-07 02:21:15 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-07 15:51:14 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-07 15:51:14 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-07 15:51:14 (4151) [[32mINFO[0m] 
* 2023-04-07 15:51:14 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-07 15:51:14 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-07 15:51:14 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-04-07 15:51:15 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-07 15:51:15 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-07 15:51:15 (4182) [[32mINFO[0m] 
* 2023-04-07 15:51:15 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-07 15:51:15 (4151) [[32mINFO[0m] 
* 2023-04-07 15:52:05 (4165) [[32mINFO[0m] http://mirror.bursabil.com.tr/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.bursabil.com.tr/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-04-07 15:52:05 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-07 15:53:01 (4165) [[32mINFO[0m] http://mirror.onlinehosting.com.tr/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.onlinehosting.com.tr/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-04-07 15:53:01 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-07 15:53:37 (4165) [[32mINFO[0m] http://kozyatagi.mirror.guzel.net.tr/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://kozyatagi.mirror.guzel.net.tr/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-04-07 15:53:37 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-07 15:53:40 (4165) [[32mINFO[0m] http://centos.vargonen.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
* 2023-04-07 15:53:40 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-07 15:54:10 (4165) [[32mINFO[0m] http://mirror.verinomi.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.verinomi.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds')
* 2023-04-07 15:54:10 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-07 15:54:47 (4165) [[32mINFO[0m] http://mirror.alastyr.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.alastyr.com/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-04-07 15:54:47 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-07 15:55:18 (4165) [[32mINFO[0m] http://mirror.saglayici.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.saglayici.com/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-04-07 15:55:18 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-07 15:56:08 (4165) [[32mINFO[0m] http://mirror.netdirekt.com.tr/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.netdirekt.com.tr/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-04-07 15:56:08 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-07 15:56:58 (4165) [[32mINFO[0m] http://mirror.centos.jt.iq/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.centos.jt.iq/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-04-07 15:56:58 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-07 15:57:34 (4165) [[32mINFO[0m] http://mirror.earthlink.iq/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.earthlink.iq/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-04-07 15:57:34 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-07 15:57:56 (4165) [[32mINFO[0m] http://mirror.bursabil.com.tr/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2a04:3880:0:16::205: Network is unreachable"
* 2023-04-07 15:57:56 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-07 15:58:31 (4165) [[32mINFO[0m] http://kozyatagi.mirror.guzel.net.tr/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://kozyatagi.mirror.guzel.net.tr/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-04-07 15:58:31 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-07 15:58:34 (4165) [[32mINFO[0m] http://centos.vargonen.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
* 2023-04-07 15:58:34 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-07 15:59:04 (4165) [[32mINFO[0m] http://mirror.verinomi.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.verinomi.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds')
* 2023-04-07 15:59:04 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-07 15:59:40 (4165) [[32mINFO[0m] http://mirror.netdirekt.com.tr/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.netdirekt.com.tr/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-04-07 15:59:40 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-07 16:00:28 (4165) [[32mINFO[0m] http://mirror.centos.jt.iq/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.centos.jt.iq/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-04-07 16:00:29 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-07 16:01:16 (4165) [[32mINFO[0m] http://mirror.alastyr.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.alastyr.com/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-04-07 16:01:16 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-07 16:01:25 (4165) [[32mINFO[0m] 
* 2023-04-07 16:01:25 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-07 16:01:25 (4182) [[32mINFO[0m] 
* 2023-04-07 16:01:25 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-07 16:01:25 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-07 16:01:25 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-07 16:01:25 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RQwyYBRrDy/ea_profile.json
* 2023-04-07 16:01:27 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/RQwyYBRrDy/ea_profile.json
* 2023-04-07 16:01:27 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-07 16:01:28 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-08 02:22:54 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-04-08 02:23:32 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-08 02:23:32 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-08 02:23:32 (4151) [[32mINFO[0m] 
* 2023-04-08 02:23:32 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-08 02:23:32 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-08 02:23:32 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-04-08 02:23:32 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-08 02:23:32 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-08 02:23:32 (4182) [[32mINFO[0m] 
* 2023-04-08 02:23:32 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-08 02:23:32 (4151) [[32mINFO[0m] 
* 2023-04-08 02:25:00 (4165) [[32mINFO[0m] 
* 2023-04-08 02:25:00 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-08 02:25:00 (4182) [[32mINFO[0m] 
* 2023-04-08 02:25:00 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-08 02:25:00 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-08 02:25:00 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-08 02:25:00 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LRs_xUB0no/ea_profile.json
* 2023-04-08 02:25:01 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/LRs_xUB0no/ea_profile.json
* 2023-04-08 02:25:01 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-08 02:25:03 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-09 02:20:07 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-09 02:20:07 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-09 02:20:07 (4151) [[32mINFO[0m] 
* 2023-04-09 02:20:08 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-09 02:20:08 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-09 02:20:08 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-04-09 02:20:08 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-09 02:20:08 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-09 02:20:08 (4182) [[32mINFO[0m] 
* 2023-04-09 02:20:08 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-09 02:20:08 (4151) [[32mINFO[0m] 
* 2023-04-09 02:20:41 (4165) [[32mINFO[0m] 
* 2023-04-09 02:20:41 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-09 02:20:41 (4182) [[32mINFO[0m] 
* 2023-04-09 02:20:41 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-09 02:20:41 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-09 02:20:41 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-09 02:20:41 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/kd40ZL77hy/ea_profile.json
* 2023-04-09 02:20:42 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/kd40ZL77hy/ea_profile.json
* 2023-04-09 02:20:42 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-09 02:20:44 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-10 02:15:49 (3805) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-04-10 02:15:49 (3806) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-04-10 02:15:49 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-10 02:15:50 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-10 02:15:50 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-10 02:15:50 (4151) [[32mINFO[0m] 
* 2023-04-10 02:15:50 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-10 02:15:50 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-10 02:15:50 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-04-10 02:15:50 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-10 02:15:50 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-10 02:15:50 (4182) [[32mINFO[0m] 
* 2023-04-10 02:15:50 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-10 02:15:50 (4151) [[32mINFO[0m] 
* 2023-04-10 02:16:34 (4165) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')
* 2023-04-10 02:16:34 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-10 02:17:05 (4165) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-10 02:17:05 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-10 02:17:58 (4165) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/97d2e9722dd5c0662a5c885a746a127e951f8860139076802e27d35eadb4aa45-comps-Everything.x86_64.xml.gz: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/97d2e9722dd5c0662a5c885a746a127e951f8860139076802e27d35eadb4aa45-comps-Everything.x86_64.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-10 02:17:58 (4165) [[32mINFO[0m] Trying other mirror.
* 2023-04-10 02:19:25 (4165) [[32mINFO[0m] 
* 2023-04-10 02:19:25 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-10 02:19:25 (4182) [[32mINFO[0m] 
* 2023-04-10 02:19:25 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-10 02:19:25 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-10 02:19:25 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-10 02:19:25 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OvEJS4STx1/ea_profile.json
* 2023-04-10 02:19:26 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/OvEJS4STx1/ea_profile.json
* 2023-04-10 02:19:26 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-10 02:19:28 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-11 02:19:49 (3805) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-04-11 02:19:49 (3806) [[31mERROR[0m] http://mirror.rabisu.com/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.rabisu.com/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-04-11 02:19:49 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-11 02:19:50 (3638) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-11 02:19:50 (4150) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-11 02:19:50 (4151) [[32mINFO[0m] 
* 2023-04-11 02:19:50 (4165) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-11 02:19:50 (4165) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-11 02:19:50 (4165) [[32mINFO[0m]               : epel extras updates
* 2023-04-11 02:19:50 (4165) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-11 02:19:50 (4165) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-11 02:19:50 (4182) [[32mINFO[0m] 
* 2023-04-11 02:19:50 (4150) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-11 02:19:50 (4151) [[32mINFO[0m] 
* 2023-04-11 02:20:50 (4165) [[32mINFO[0m] 
* 2023-04-11 02:20:50 (4165) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-11 02:20:50 (4182) [[32mINFO[0m] 
* 2023-04-11 02:20:50 (3646) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-11 02:20:50 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-11 02:20:50 (3298) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-11 02:20:50 (1740) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/A3FFy1jkS5/ea_profile.json
* 2023-04-11 02:20:52 (1765) [[32mINFO[0m] Backed up EA4 profile to /tmp/A3FFy1jkS5/ea_profile.json
* 2023-04-11 02:20:52 (2820) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-11 02:20:55 (759) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-12 02:19:19 (372) [[32mINFO[0m] Self-update of script version 6 requested.
* 2023-04-12 02:19:19 (377) [[32mINFO[0m] Newer version of script found. Downloading.
* 2023-04-12 02:19:20 (386) [[32mINFO[0m] Script update to version 7 successful.
* 2023-04-12 02:19:57 (3686) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-12 02:19:57 (4198) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-12 02:19:57 (4199) [[32mINFO[0m] 
* 2023-04-12 02:19:57 (4213) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-12 02:19:57 (4213) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-12 02:19:57 (4213) [[32mINFO[0m]               : epel extras updates
* 2023-04-12 02:19:58 (4213) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-12 02:19:58 (4213) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-12 02:19:58 (4230) [[32mINFO[0m] 
* 2023-04-12 02:19:58 (4198) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-12 02:19:58 (4199) [[32mINFO[0m] 
* 2023-04-12 02:24:37 (4213) [[32mINFO[0m] 
* 2023-04-12 02:24:37 (4213) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-12 02:24:37 (4230) [[32mINFO[0m] 
* 2023-04-12 02:24:37 (3694) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-12 02:24:37 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-12 02:24:37 (3346) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-12 02:24:39 (1780) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NGmmQ5OKYA/ea_profile.json
* 2023-04-12 02:24:41 (1805) [[32mINFO[0m] Backed up EA4 profile to /tmp/NGmmQ5OKYA/ea_profile.json
* 2023-04-12 02:24:41 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-12 02:24:42 (797) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-13 02:27:14 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-04-13 02:28:29 (3686) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-13 02:28:29 (4198) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-13 02:28:29 (4199) [[32mINFO[0m] 
* 2023-04-13 02:28:29 (4213) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-13 02:28:29 (4213) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-13 02:28:29 (4213) [[32mINFO[0m]               : epel extras updates
* 2023-04-13 02:28:30 (4213) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-13 02:28:30 (4213) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-13 02:28:30 (4230) [[32mINFO[0m] 
* 2023-04-13 02:28:30 (4198) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-13 02:28:30 (4199) [[32mINFO[0m] 
* 2023-04-13 02:29:03 (4213) [[32mINFO[0m] 
* 2023-04-13 02:29:03 (4213) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-13 02:29:04 (4230) [[32mINFO[0m] 
* 2023-04-13 02:29:04 (3694) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-13 02:29:04 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-13 02:29:04 (3346) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-13 02:29:04 (1780) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MbJFIjsg0R/ea_profile.json
* 2023-04-13 02:29:05 (1805) [[32mINFO[0m] Backed up EA4 profile to /tmp/MbJFIjsg0R/ea_profile.json
* 2023-04-13 02:29:05 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-13 02:29:07 (797) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-14 02:19:49 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-04-14 02:20:04 (3686) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-14 02:20:04 (4198) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-14 02:20:04 (4199) [[32mINFO[0m] 
* 2023-04-14 02:20:04 (4213) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-14 02:20:04 (4213) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-14 02:20:04 (4213) [[32mINFO[0m]               : epel extras updates
* 2023-04-14 02:20:05 (4213) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-14 02:20:05 (4213) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-14 02:20:05 (4230) [[32mINFO[0m] 
* 2023-04-14 02:20:05 (4198) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-14 02:20:05 (4199) [[32mINFO[0m] 
* 2023-04-14 02:20:47 (4213) [[32mINFO[0m] 
* 2023-04-14 02:20:47 (4213) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-14 02:20:48 (4230) [[32mINFO[0m] 
* 2023-04-14 02:20:48 (3694) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-14 02:20:48 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-14 02:20:48 (3346) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-14 02:20:48 (1780) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/n_kmMtiBVq/ea_profile.json
* 2023-04-14 02:20:49 (1805) [[32mINFO[0m] Backed up EA4 profile to /tmp/n_kmMtiBVq/ea_profile.json
* 2023-04-14 02:20:49 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-14 02:20:52 (797) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-14 15:52:35 (3853) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-04-14 15:52:35 (3854) [[31mERROR[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/8fa65a740e1fcf58cc82ee2426f0ae143c4eb606f2e02a9cb41663b551344fba-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.earthlink.iq/epel/7/x86_64/repodata/2e82fbefb4e6cc18174b922f1bf247440e60992333ce74ba11498429454b7094-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.earthlink.iq/epel/7/x86_64/repodata/2e82fbefb4e6cc18174b922f1bf247440e60992333ce74ba11498429454b7094-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/2e82fbefb4e6cc18174b922f1bf247440e60992333ce74ba11498429454b7094-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
* 2023-04-14 15:52:35 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-14 15:52:35 (3686) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-14 15:52:35 (4198) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-14 15:52:35 (4199) [[32mINFO[0m] 
* 2023-04-14 15:52:36 (4213) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-14 15:52:36 (4213) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-14 15:52:36 (4213) [[32mINFO[0m]               : epel extras updates
* 2023-04-14 15:52:36 (4213) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-14 15:52:36 (4213) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-14 15:52:36 (4230) [[32mINFO[0m] 
* 2023-04-14 15:52:36 (4198) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-14 15:52:36 (4199) [[32mINFO[0m] 
* 2023-04-14 15:52:53 (4213) [[32mINFO[0m] https://mirror.ps.kz/epel/7/x86_64/repodata/8093cccb2ec2c427a84833011c6f893c3fdaa2fd69ee82024ca1fe303fae7378-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-04-14 15:52:53 (4213) [[32mINFO[0m] Trying other mirror.
* 2023-04-14 15:52:53 (4213) [[32mINFO[0m] To address this issue please refer to the below wiki article 
* 2023-04-14 15:52:53 (4213) [[32mINFO[0m] 
* 2023-04-14 15:52:53 (4213) [[32mINFO[0m] https://wiki.centos.org/yum-errors
* 2023-04-14 15:52:53 (4213) [[32mINFO[0m] 
* 2023-04-14 15:52:53 (4213) [[32mINFO[0m] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2023-04-14 15:52:53 (4213) [[32mINFO[0m] 
* 2023-04-14 15:52:57 (4213) [[32mINFO[0m] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/8093cccb2ec2c427a84833011c6f893c3fdaa2fd69ee82024ca1fe303fae7378-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-04-14 15:52:57 (4213) [[32mINFO[0m] Trying other mirror.
* 2023-04-14 15:53:14 (4213) [[32mINFO[0m] 
* 2023-04-14 15:53:14 (4213) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-14 15:53:14 (4230) [[32mINFO[0m] 
* 2023-04-14 15:53:14 (3694) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-14 15:53:14 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-14 15:53:14 (3346) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-14 15:53:14 (1780) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/E6rdJc0QCs/ea_profile.json
* 2023-04-14 15:53:15 (1805) [[32mINFO[0m] Backed up EA4 profile to /tmp/E6rdJc0QCs/ea_profile.json
* 2023-04-14 15:53:15 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-14 15:53:17 (797) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-15 02:18:53 (3853) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-04-15 02:18:53 (3854) [[31mERROR[0m] http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/96b328a2f936c1ff5659d40dfb4e32a6da941e7f5046bb768ae8d9beffb23a92-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: [Errno 12] Timeout on http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: [Errno 12] Timeout on http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://repo.boun.edu.tr/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.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/.

http://208.74.123.61/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://184.94.196.92/cpanelsync/repos/CentOS/7/EA4/repodata/96b328a2f936c1ff5659d40dfb4e32a6da941e7f5046bb768ae8d9beffb23a92-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://208.74.123.61/cpanelsync/repos/CentOS/7/EA4/repodata/96b328a2f936c1ff5659d40dfb4e32a6da941e7f5046bb768ae8d9beffb23a92-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://201.159.169.169/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://185.15.22.168/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: [Errno 12] Timeout on http://185.15.22.168/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://103.15.48.49/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: [Errno 12] Timeout on http://103.15.48.49/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://185.157.208.252/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://63.247.64.58/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: [Errno 12] Timeout on http://63.247.64.58/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://203.174.85.202/cpanelsync/repos/CentOS/7/EA4/repodata/96b328a2f936c1ff5659d40dfb4e32a6da941e7f5046bb768ae8d9beffb23a92-other.sqlite.bz2: [Errno 12] Timeout on http://203.174.85.202/cpanelsync/repos/CentOS/7/EA4/repodata/96b328a2f936c1ff5659d40dfb4e32a6da941e7f5046bb768ae8d9beffb23a92-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/96b328a2f936c1ff5659d40dfb4e32a6da941e7f5046bb768ae8d9beffb23a92-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://118.88.24.67/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: [Errno 12] Timeout on http://118.88.24.67/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://103.120.66.133/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: [Errno 12] Timeout on http://103.120.66.133/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://103.72.162.35/cpanelsync/repos/CentOS/7/EA4/repodata/96b328a2f936c1ff5659d40dfb4e32a6da941e7f5046bb768ae8d9beffb23a92-other.sqlite.bz2: [Errno 12] Timeout on http://103.72.162.35/cpanelsync/repos/CentOS/7/EA4/repodata/96b328a2f936c1ff5659d40dfb4e32a6da941e7f5046bb768ae8d9beffb23a92-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/96b328a2f936c1ff5659d40dfb4e32a6da941e7f5046bb768ae8d9beffb23a92-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-04-15 02:18:53 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-15 02:18:53 (3686) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-15 02:18:53 (4198) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-15 02:18:53 (4199) [[32mINFO[0m] 
* 2023-04-15 02:18:54 (4213) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-15 02:18:54 (4213) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-15 02:18:54 (4213) [[32mINFO[0m]               : epel extras updates
* 2023-04-15 02:18:54 (4213) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-15 02:18:54 (4213) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-15 02:18:54 (4230) [[32mINFO[0m] 
* 2023-04-15 02:18:54 (4198) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-15 02:18:54 (4199) [[32mINFO[0m] 
* 2023-04-15 02:19:38 (4213) [[32mINFO[0m] 
* 2023-04-15 02:19:38 (4213) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-15 02:19:38 (4230) [[32mINFO[0m] 
* 2023-04-15 02:19:38 (3694) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-15 02:19:38 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-15 02:19:38 (3346) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-15 02:19:38 (1780) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/eybxI8k1Mb/ea_profile.json
* 2023-04-15 02:19:40 (1805) [[32mINFO[0m] Backed up EA4 profile to /tmp/eybxI8k1Mb/ea_profile.json
* 2023-04-15 02:19:40 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-15 02:19:42 (797) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-16 02:20:03 (3686) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-16 02:20:03 (4198) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-16 02:20:03 (4199) [[32mINFO[0m] 
* 2023-04-16 02:20:03 (4213) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-16 02:20:03 (4213) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-16 02:20:03 (4213) [[32mINFO[0m]               : epel extras updates
* 2023-04-16 02:20:04 (4213) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-16 02:20:04 (4213) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-16 02:20:04 (4230) [[32mINFO[0m] 
* 2023-04-16 02:20:04 (4198) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-16 02:20:04 (4199) [[32mINFO[0m] 
* 2023-04-16 02:21:43 (4213) [[32mINFO[0m] 
* 2023-04-16 02:21:43 (4213) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-16 02:21:44 (4230) [[32mINFO[0m] 
* 2023-04-16 02:21:44 (3694) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-16 02:21:44 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-16 02:21:44 (3346) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-16 02:21:45 (1780) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Kkdo34Bjaq/ea_profile.json
* 2023-04-16 02:21:47 (1805) [[32mINFO[0m] Backed up EA4 profile to /tmp/Kkdo34Bjaq/ea_profile.json
* 2023-04-16 02:21:47 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-16 02:21:49 (797) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-17 02:18:41 (3853) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-04-17 02:18:41 (3854) [[31mERROR[0m] http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: [Errno 12] Timeout on http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/97d2e9722dd5c0662a5c885a746a127e951f8860139076802e27d35eadb4aa45-comps-Everything.x86_64.xml.gz: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/97d2e9722dd5c0662a5c885a746a127e951f8860139076802e27d35eadb4aa45-comps-Everything.x86_64.xml.gz: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')
Trying other mirror.
http://208.100.0.204/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/88098d96e0c6ae79b83bfbc0a9be7c6999cde1f548c98be1453051ba86de6d89-filelists.sqlite.bz2: [Errno 12] Timeout on http://208.100.0.204/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/88098d96e0c6ae79b83bfbc0a9be7c6999cde1f548c98be1453051ba86de6d89-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: [Errno 12] Timeout on http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/5654d80c4fb897bef61a98538843ff510c7ca9a31dad71d02e787d58a8bec1ab-other.sqlite.bz2: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/5654d80c4fb897bef61a98538843ff510c7ca9a31dad71d02e787d58a8bec1ab-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/88098d96e0c6ae79b83bfbc0a9be7c6999cde1f548c98be1453051ba86de6d89-filelists.sqlite.bz2: [Errno 12] Timeout on http://178.18.193.52/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/88098d96e0c6ae79b83bfbc0a9be7c6999cde1f548c98be1453051ba86de6d89-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror-icn.misakamikoto.network/fedora-epel/7/x86_64/repodata/5654d80c4fb897bef61a98538843ff510c7ca9a31dad71d02e787d58a8bec1ab-other.sqlite.bz2: [Errno 12] Timeout on https://mirror-icn.misakamikoto.network/fedora-epel/7/x86_64/repodata/5654d80c4fb897bef61a98538843ff510c7ca9a31dad71d02e787d58a8bec1ab-other.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')
Trying other mirror.
http://103.101.161.235/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: [Errno 12] Timeout on http://103.101.161.235/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: [Errno 12] Timeout on http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirror.earthlink.iq/centos/7.9.2009/updates/x86_64/repodata/da648f33f2b60aeb3ae3c26d2fbbc7587c86d2b3c4dd8f97cf085d38735438c9-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.earthlink.iq/centos/7.9.2009/updates/x86_64/repodata/da648f33f2b60aeb3ae3c26d2fbbc7587c86d2b3c4dd8f97cf085d38735438c9-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.74.123.62/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/88098d96e0c6ae79b83bfbc0a9be7c6999cde1f548c98be1453051ba86de6d89-filelists.sqlite.bz2: [Errno 12] Timeout on http://208.74.123.62/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/88098d96e0c6ae79b83bfbc0a9be7c6999cde1f548c98be1453051ba86de6d89-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: [Errno 12] Timeout on http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror-hnd.misakamikoto.network/fedora-epel/7/x86_64/repodata/5654d80c4fb897bef61a98538843ff510c7ca9a31dad71d02e787d58a8bec1ab-other.sqlite.bz2: [Errno 12] Timeout on https://mirror-hnd.misakamikoto.network/fedora-epel/7/x86_64/repodata/5654d80c4fb897bef61a98538843ff510c7ca9a31dad71d02e787d58a8bec1ab-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.94/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://103.252.152.1/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: [Errno 12] Timeout on http://103.252.152.1/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://103.252.152.1/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/88098d96e0c6ae79b83bfbc0a9be7c6999cde1f548c98be1453051ba86de6d89-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-04-17 02:18:41 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-17 02:18:41 (3686) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-17 02:18:41 (4198) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-17 02:18:41 (4199) [[32mINFO[0m] 
* 2023-04-17 02:18:42 (4213) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-17 02:18:42 (4213) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-17 02:18:42 (4213) [[32mINFO[0m]               : epel extras updates
* 2023-04-17 02:18:44 (4213) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-17 02:18:44 (4213) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-17 02:18:44 (4230) [[32mINFO[0m] 
* 2023-04-17 02:18:44 (4198) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-17 02:18:44 (4199) [[32mINFO[0m] 
* 2023-04-17 02:21:08 (4213) [[32mINFO[0m] 
* 2023-04-17 02:21:08 (4213) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-17 02:21:09 (4230) [[32mINFO[0m] 
* 2023-04-17 02:21:09 (3694) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-17 02:21:09 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-17 02:21:09 (3346) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-17 02:21:09 (1780) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/I34YTaVNf3/ea_profile.json
* 2023-04-17 02:21:10 (1805) [[32mINFO[0m] Backed up EA4 profile to /tmp/I34YTaVNf3/ea_profile.json
* 2023-04-17 02:21:10 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-17 02:21:12 (797) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-18 02:23:24 (3853) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-04-18 02:23:24 (3854) [[31mERROR[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')
Trying other mirror.
http://45.228.65.220/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://184.94.196.92/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.92/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://45.228.65.220/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: [Errno 12] Timeout on http://45.228.65.220/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/97d2e9722dd5c0662a5c885a746a127e951f8860139076802e27d35eadb4aa45-comps-Everything.x86_64.xml.gz: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/97d2e9722dd5c0662a5c885a746a127e951f8860139076802e27d35eadb4aa45-comps-Everything.x86_64.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://epel.mirror.angkasa.id/pub/epel/7/x86_64/repodata/74eddfe8351d1d542e1cec407559ec6a99d36c6516b3e31a9f0259df42a9b227-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://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/a2f11efec92388eae19a4434377faf8e0944b078396e5fe9df7f9a592a1b2074-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/9bb930f0be560972926c9dd99be84f4eddb82207735c1f64f41a9d58c695c7ee-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-04-18 02:23:24 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-18 02:23:24 (3686) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-18 02:23:24 (4198) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-18 02:23:24 (4199) [[32mINFO[0m] 
* 2023-04-18 02:23:25 (4213) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-18 02:23:25 (4213) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-18 02:23:25 (4213) [[32mINFO[0m]               : epel extras updates
* 2023-04-18 02:23:25 (4213) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-18 02:23:25 (4213) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-18 02:23:25 (4230) [[32mINFO[0m] 
* 2023-04-18 02:23:25 (4198) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-18 02:23:25 (4199) [[32mINFO[0m] 
* 2023-04-18 02:23:58 (4213) [[32mINFO[0m] 
* 2023-04-18 02:23:58 (4213) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-18 02:23:58 (4230) [[32mINFO[0m] 
* 2023-04-18 02:23:58 (3694) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-18 02:23:58 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-18 02:23:58 (3346) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-18 02:23:58 (1780) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/e4gNmLm34Y/ea_profile.json
* 2023-04-18 02:23:59 (1805) [[32mINFO[0m] Backed up EA4 profile to /tmp/e4gNmLm34Y/ea_profile.json
* 2023-04-18 02:23:59 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-18 02:24:02 (797) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-19 02:16:26 (3853) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-04-19 02:16:26 (3854) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-04-19 02:16:26 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-19 02:16:26 (3686) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-19 02:16:26 (4198) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-19 02:16:26 (4199) [[32mINFO[0m] 
* 2023-04-19 02:16:26 (4213) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-19 02:16:27 (4213) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-19 02:16:27 (4213) [[32mINFO[0m]               : epel extras updates
* 2023-04-19 02:16:27 (4213) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-19 02:16:27 (4213) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-19 02:16:27 (4230) [[32mINFO[0m] 
* 2023-04-19 02:16:27 (4198) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-19 02:16:27 (4199) [[32mINFO[0m] 
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m] 
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m] 
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m] 
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m] 
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m] 
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m] 
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m] 
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]         or
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m] 
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]         compromise:
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m] 
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m] 
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-04-19 02:17:08 (4230) [[32mINFO[0m] 
* 2023-04-19 02:17:08 (3694) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-19 02:17:08 (3709) [[32mINFO[0m] Checking /scripts/sysup
* 2023-04-19 02:17:08 (4198) [[32mINFO[0m] Running: /scripts/sysup
* 2023-04-19 02:17:08 (4199) [[32mINFO[0m] 
* 2023-04-19 02:17:08 (4213) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-04-19 02:17:09 (4213) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-04-19 02:17:09 (4230) [[32mINFO[0m] 
* 2023-04-19 02:17:09 (3346) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-19 02:17:09 (1780) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MEcgvwyLw3/ea_profile.json
* 2023-04-19 02:20:39 (1805) [[32mINFO[0m] Backed up EA4 profile to /tmp/MEcgvwyLw3/ea_profile.json
* 2023-04-19 02:20:39 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-19 02:20:41 (797) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-20 02:21:57 (3686) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-20 02:21:57 (4198) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-20 02:21:57 (4199) [[32mINFO[0m] 
* 2023-04-20 02:21:57 (4213) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-20 02:21:58 (4213) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-20 02:21:58 (4213) [[32mINFO[0m]               : epel extras updates
* 2023-04-20 02:21:58 (4213) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-20 02:21:58 (4213) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-20 02:21:58 (4230) [[32mINFO[0m] 
* 2023-04-20 02:21:58 (4198) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-20 02:21:58 (4199) [[32mINFO[0m] 
* 2023-04-20 02:26:15 (4213) [[32mINFO[0m] 
* 2023-04-20 02:26:15 (4213) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-20 02:26:16 (4230) [[32mINFO[0m] 
* 2023-04-20 02:26:16 (3694) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-20 02:26:16 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-20 02:26:16 (3346) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-20 02:26:16 (1780) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/r_D1j28Mif/ea_profile.json
* 2023-04-20 02:26:17 (1805) [[32mINFO[0m] Backed up EA4 profile to /tmp/r_D1j28Mif/ea_profile.json
* 2023-04-20 02:26:17 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-20 02:26:19 (797) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-21 02:13:43 (3853) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-04-21 02:13:43 (3854) [[31mERROR[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
14: curl#52 - "Empty reply from server"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2023-04-21 02:13:43 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-21 02:13:44 (3686) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-21 02:13:44 (4198) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-21 02:13:44 (4199) [[32mINFO[0m] 
* 2023-04-21 02:13:44 (4213) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-21 02:13:44 (4213) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-21 02:13:44 (4213) [[32mINFO[0m]               : epel extras updates
* 2023-04-21 02:13:44 (4213) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-21 02:13:44 (4213) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-21 02:13:44 (4230) [[32mINFO[0m] 
* 2023-04-21 02:13:44 (4198) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-21 02:13:44 (4199) [[32mINFO[0m] 
* 2023-04-21 02:14:46 (4213) [[32mINFO[0m] https://mirror.yer.az/fedora-epel/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://mirror.yer.az/fedora-epel/7/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')
* 2023-04-21 02:14:46 (4213) [[32mINFO[0m] Trying other mirror.
* 2023-04-21 02:16:37 (4213) [[32mINFO[0m] http://mirror.radoreservers.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.radoreservers.com/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-04-21 02:16:37 (4213) [[32mINFO[0m] Trying other mirror.
* 2023-04-21 02:16:53 (4213) [[32mINFO[0m] 
* 2023-04-21 02:16:53 (4213) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-21 02:16:53 (4230) [[32mINFO[0m] 
* 2023-04-21 02:16:53 (3694) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-21 02:16:53 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-21 02:16:53 (3346) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-21 02:16:53 (1780) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Kayhq0aiQD/ea_profile.json
* 2023-04-21 02:16:54 (1805) [[32mINFO[0m] Backed up EA4 profile to /tmp/Kayhq0aiQD/ea_profile.json
* 2023-04-21 02:16:54 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-21 02:16:56 (797) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-21 15:58:41 (3686) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-21 15:58:41 (4198) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-21 15:58:41 (4199) [[32mINFO[0m] 
* 2023-04-21 15:58:41 (4213) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-21 15:58:41 (4213) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-21 15:58:41 (4213) [[32mINFO[0m]               : epel extras updates
* 2023-04-21 15:58:41 (4213) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-21 15:58:41 (4213) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-21 15:58:41 (4230) [[32mINFO[0m] 
* 2023-04-21 15:58:41 (4198) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-21 15:58:41 (4199) [[32mINFO[0m] 
* 2023-04-21 16:04:17 (4213) [[32mINFO[0m] 
* 2023-04-21 16:04:17 (4213) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-21 16:04:17 (4230) [[32mINFO[0m] 
* 2023-04-21 16:04:17 (3694) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-21 16:04:17 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-21 16:04:17 (3346) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-21 16:04:17 (1780) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Csp2BL1ZlI/ea_profile.json
* 2023-04-21 16:04:19 (1805) [[32mINFO[0m] Backed up EA4 profile to /tmp/Csp2BL1ZlI/ea_profile.json
* 2023-04-21 16:04:19 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-21 16:04:26 (797) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-22 02:14:28 (3686) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-22 02:14:28 (4198) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-22 02:14:28 (4199) [[32mINFO[0m] 
* 2023-04-22 02:14:28 (4213) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-22 02:14:28 (4213) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-22 02:14:28 (4213) [[32mINFO[0m]               : epel extras updates
* 2023-04-22 02:14:28 (4213) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-22 02:14:28 (4213) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-22 02:14:28 (4230) [[32mINFO[0m] 
* 2023-04-22 02:14:28 (4198) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-22 02:14:28 (4199) [[32mINFO[0m] 
* 2023-04-22 02:14:59 (4213) [[32mINFO[0m] 
* 2023-04-22 02:14:59 (4213) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-22 02:14:59 (4230) [[32mINFO[0m] 
* 2023-04-22 02:14:59 (3694) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-22 02:14:59 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-22 02:14:59 (3346) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-22 02:14:59 (1780) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7jrxIDihIL/ea_profile.json
* 2023-04-22 02:15:00 (1805) [[32mINFO[0m] Backed up EA4 profile to /tmp/7jrxIDihIL/ea_profile.json
* 2023-04-22 02:15:00 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-22 02:15:02 (797) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-23 02:15:25 (3686) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-23 02:15:25 (4198) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-23 02:15:25 (4199) [[32mINFO[0m] 
* 2023-04-23 02:15:25 (4213) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-23 02:15:25 (4213) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-23 02:15:25 (4213) [[32mINFO[0m]               : epel extras updates
* 2023-04-23 02:15:25 (4213) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-23 02:15:25 (4213) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-23 02:15:25 (4230) [[32mINFO[0m] 
* 2023-04-23 02:15:25 (4198) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-23 02:15:25 (4199) [[32mINFO[0m] 
* 2023-04-23 02:16:49 (4213) [[32mINFO[0m] 
* 2023-04-23 02:16:49 (4213) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-23 02:16:49 (4230) [[32mINFO[0m] 
* 2023-04-23 02:16:49 (3694) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-23 02:16:49 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-23 02:16:49 (3346) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-23 02:16:49 (1780) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QPUhCBuPcx/ea_profile.json
* 2023-04-23 02:16:51 (1805) [[32mINFO[0m] Backed up EA4 profile to /tmp/QPUhCBuPcx/ea_profile.json
* 2023-04-23 02:16:51 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-23 02:16:52 (797) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-24 02:14:55 (3853) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-04-24 02:14:55 (3854) [[31mERROR[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/cpanel-plugins-c7-x86_64-mirrorlist error was
14: curl#52 - "Empty reply from server"
* 2023-04-24 02:14:55 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-24 02:14:56 (3686) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-24 02:14:56 (4198) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-24 02:14:56 (4199) [[32mINFO[0m] 
* 2023-04-24 02:14:56 (4213) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-24 02:14:56 (4213) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-24 02:14:56 (4213) [[32mINFO[0m]               : epel extras updates
* 2023-04-24 02:14:56 (4213) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-24 02:14:57 (4213) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-24 02:14:57 (4230) [[32mINFO[0m] 
* 2023-04-24 02:14:57 (4198) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-24 02:14:57 (4199) [[32mINFO[0m] 
* 2023-04-24 02:16:09 (4213) [[32mINFO[0m] http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/790e83610f5360247ffa19c73fcbad00ea26b05e4ec03e562a0ba2d387fbd994-primary.sqlite.bz2: [Errno 12] Timeout on http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/790e83610f5360247ffa19c73fcbad00ea26b05e4ec03e562a0ba2d387fbd994-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-24 02:16:09 (4213) [[32mINFO[0m] Trying other mirror.
* 2023-04-24 02:16:35 (4213) [[32mINFO[0m] http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/790e83610f5360247ffa19c73fcbad00ea26b05e4ec03e562a0ba2d387fbd994-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-04-24 02:16:35 (4213) [[32mINFO[0m] Trying other mirror.
* 2023-04-24 02:16:54 (4213) [[32mINFO[0m] 
* 2023-04-24 02:16:54 (4213) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-24 02:16:54 (4230) [[32mINFO[0m] 
* 2023-04-24 02:16:54 (3694) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-24 02:16:54 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-24 02:16:54 (3346) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-24 02:16:55 (1780) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/eetchH5KUB/ea_profile.json
* 2023-04-24 02:16:58 (1805) [[32mINFO[0m] Backed up EA4 profile to /tmp/eetchH5KUB/ea_profile.json
* 2023-04-24 02:16:58 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-24 02:17:00 (797) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-25 02:19:27 (3686) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-25 02:19:27 (4198) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-25 02:19:27 (4199) [[32mINFO[0m] 
* 2023-04-25 02:19:27 (4213) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-25 02:19:28 (4213) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-25 02:19:28 (4213) [[32mINFO[0m]               : epel extras updates
* 2023-04-25 02:19:28 (4213) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-25 02:19:28 (4213) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-25 02:19:28 (4230) [[32mINFO[0m] 
* 2023-04-25 02:19:28 (4198) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-25 02:19:28 (4199) [[32mINFO[0m] 
* 2023-04-25 02:20:23 (4213) [[32mINFO[0m] 
* 2023-04-25 02:20:23 (4213) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-25 02:20:24 (4230) [[32mINFO[0m] 
* 2023-04-25 02:20:24 (3694) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-25 02:20:24 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-25 02:20:24 (3346) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-25 02:20:24 (1780) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vpwUv7FHHm/ea_profile.json
* 2023-04-25 02:20:25 (1805) [[32mINFO[0m] Backed up EA4 profile to /tmp/vpwUv7FHHm/ea_profile.json
* 2023-04-25 02:20:25 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-25 02:20:26 (797) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-26 02:16:30 (3686) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-26 02:16:30 (4198) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-26 02:16:30 (4199) [[32mINFO[0m] 
* 2023-04-26 02:16:30 (4213) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-26 02:16:30 (4213) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-26 02:16:30 (4213) [[32mINFO[0m]               : epel extras updates
* 2023-04-26 02:16:30 (4213) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2023-04-26 02:16:30 (4213) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-26 02:16:30 (4230) [[32mINFO[0m] 
* 2023-04-26 02:16:30 (4198) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-26 02:16:30 (4199) [[32mINFO[0m] 
* 2023-04-26 02:17:22 (4213) [[32mINFO[0m] 
* 2023-04-26 02:17:22 (4213) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-26 02:17:23 (4230) [[32mINFO[0m] 
* 2023-04-26 02:17:23 (3694) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-26 02:17:23 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-26 02:17:23 (3346) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-26 02:17:23 (1780) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FLVhAUoN0k/ea_profile.json
* 2023-04-26 02:17:24 (1805) [[32mINFO[0m] Backed up EA4 profile to /tmp/FLVhAUoN0k/ea_profile.json
* 2023-04-26 02:17:24 (2856) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2023-04-26 02:17:26 (797) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-27 02:21:51 (410) [[32mINFO[0m] Self-update of script version 7 requested.
* 2023-04-27 02:21:52 (415) [[32mINFO[0m] Newer version of script found. Downloading.
* 2023-04-27 02:21:53 (424) [[32mINFO[0m] Script update to version 8 successful.
* 2023-04-27 02:21:56 (1573) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-27 02:21:56 (3853) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-27 02:21:56 (3854) [[32mINFO[0m] 
* 2023-04-27 02:21:56 (3867) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-27 02:21:56 (3867) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-27 02:21:56 (3867) [[32mINFO[0m]               : epel extras updates
* 2023-04-27 02:21:56 (3867) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-27 02:21:56 (3884) [[32mINFO[0m] 
* 2023-04-27 02:21:56 (3853) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-27 02:21:56 (3854) [[32mINFO[0m] 
* 2023-04-27 02:23:27 (3867) [[32mINFO[0m] 
* 2023-04-27 02:23:27 (3867) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-27 02:23:28 (3884) [[32mINFO[0m] 
* 2023-04-27 02:23:28 (1580) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-27 02:23:28 (144) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-27 02:24:09 (681) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-27 02:24:09 (2015) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Fh1nCmYlEJ/ea_profile.json
* 2023-04-27 02:24:11 (2038) [[32mINFO[0m] Backed up EA4 profile to /tmp/Fh1nCmYlEJ/ea_profile.json
* 2023-04-27 02:24:12 (244) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-28 02:16:17 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-04-28 02:16:18 (1573) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-28 02:16:18 (3853) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-28 02:16:18 (3854) [[32mINFO[0m] 
* 2023-04-28 02:16:19 (3867) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-28 02:16:19 (3867) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-28 02:16:19 (3867) [[32mINFO[0m]               : epel extras updates
* 2023-04-28 02:16:21 (3867) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-28 02:16:21 (3884) [[32mINFO[0m] 
* 2023-04-28 02:16:21 (3853) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-28 02:16:21 (3854) [[32mINFO[0m] 
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m] 12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m] 
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m] 
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m] 
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m] 
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m] 
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m] 
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m] 
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]         or
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m] 
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]         compromise:
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m] 
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m] 
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m] Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2023-04-28 02:16:55 (3884) [[32mINFO[0m] 
* 2023-04-28 02:16:55 (1580) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-28 02:16:55 (1594) [[32mINFO[0m] Checking /scripts/sysup
* 2023-04-28 02:16:55 (3853) [[32mINFO[0m] Running: /scripts/sysup
* 2023-04-28 02:16:55 (3854) [[32mINFO[0m] 
* 2023-04-28 02:16:55 (3867) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-04-28 02:16:56 (3867) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-04-28 02:16:56 (3884) [[32mINFO[0m] 
* 2023-04-28 02:17:02 (1439) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-04-28 02:17:02 (1440) [[31mERROR[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
14: curl#52 - "Empty reply from server"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2023-04-28 02:17:02 (144) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-28 02:17:03 (681) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-28 02:17:03 (2015) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8sYRGq6V7Q/ea_profile.json
* 2023-04-28 02:18:19 (2038) [[32mINFO[0m] Backed up EA4 profile to /tmp/8sYRGq6V7Q/ea_profile.json
* 2023-04-28 02:18:20 (244) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-28 15:55:03 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-04-28 15:55:04 (1573) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-28 15:55:04 (3853) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-28 15:55:04 (3854) [[32mINFO[0m] 
* 2023-04-28 15:55:04 (3867) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-28 15:55:04 (3867) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-28 15:55:04 (3867) [[32mINFO[0m]               : epel extras updates
* 2023-04-28 15:55:04 (3867) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-28 15:55:04 (3884) [[32mINFO[0m] 
* 2023-04-28 15:55:04 (3853) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-28 15:55:04 (3854) [[32mINFO[0m] 
* 2023-04-28 15:55:54 (3867) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/1e4212b3cab83e8f3476266fc38d556accd40ac6b3a2011f654c7988772a81d0-updateinfo.xml.bz2: [Errno 12] Timeout on http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/1e4212b3cab83e8f3476266fc38d556accd40ac6b3a2011f654c7988772a81d0-updateinfo.xml.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 15:55:54 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 15:56:03 (3867) [[32mINFO[0m] http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno 12] Timeout on http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 15:56:03 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 15:56:14 (3867) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/97d2e9722dd5c0662a5c885a746a127e951f8860139076802e27d35eadb4aa45-comps-Everything.x86_64.xml.gz: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/97d2e9722dd5c0662a5c885a746a127e951f8860139076802e27d35eadb4aa45-comps-Everything.x86_64.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 15:56:14 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 15:56:30 (3867) [[32mINFO[0m] http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-04-28 15:56:30 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 15:57:06 (3867) [[32mINFO[0m] http://epel.mirror.angkasa.id/pub/epel/7/x86_64/repodata/1e4212b3cab83e8f3476266fc38d556accd40ac6b3a2011f654c7988772a81d0-updateinfo.xml.bz2: [Errno 12] Timeout on http://epel.mirror.angkasa.id/pub/epel/7/x86_64/repodata/1e4212b3cab83e8f3476266fc38d556accd40ac6b3a2011f654c7988772a81d0-updateinfo.xml.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 15:57:06 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 15:57:10 (3867) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/c1fd3ac0f66944e6559738b8f5732fa598a88f30856dfa0dce3b64379f3f2ad6-primary.sqlite.bz2: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/c1fd3ac0f66944e6559738b8f5732fa598a88f30856dfa0dce3b64379f3f2ad6-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 15:57:10 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 15:57:14 (3867) [[32mINFO[0m] http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno 12] Timeout on http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 15:57:14 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 15:57:50 (3867) [[32mINFO[0m] https://repo.extreme-ix.org/epel/7/x86_64/repodata/1e4212b3cab83e8f3476266fc38d556accd40ac6b3a2011f654c7988772a81d0-updateinfo.xml.bz2: [Errno 12] Timeout on https://repo.extreme-ix.org/epel/7/x86_64/repodata/1e4212b3cab83e8f3476266fc38d556accd40ac6b3a2011f654c7988772a81d0-updateinfo.xml.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 15:57:50 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 15:58:42 (3867) [[32mINFO[0m] http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno 12] Timeout on http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 15:58:42 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 16:00:00 (3867) [[32mINFO[0m] http://103.17.8.8/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno 12] Timeout on http://103.17.8.8/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 16:00:00 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 16:01:45 (3867) [[32mINFO[0m] http://103.101.161.235/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno 12] Timeout on http://103.101.161.235/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 16:01:45 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 16:02:09 (3867) [[32mINFO[0m] http://184.94.196.94/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-04-28 16:02:09 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 16:06:37 (3867) [[32mINFO[0m] http://103.48.119.120/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno 12] Timeout on http://103.48.119.120/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 16:06:37 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 16:08:26 (3867) [[32mINFO[0m] http://27.50.85.8/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno 12] Timeout on http://27.50.85.8/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 16:08:26 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 16:10:17 (3867) [[32mINFO[0m] http://103.120.66.133/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno 12] Timeout on http://103.120.66.133/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 16:10:17 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 16:10:25 (3867) [[32mINFO[0m] http://118.88.24.67/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
* 2023-04-28 16:10:25 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 16:11:13 (3867) [[32mINFO[0m] http://208.74.123.61/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-04-28 16:11:13 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 16:12:42 (3867) [[32mINFO[0m] http://45.228.65.220/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno 12] Timeout on http://45.228.65.220/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 16:12:42 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 16:13:29 (3867) [[32mINFO[0m] http://203.174.85.202/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno 12] Timeout on http://203.174.85.202/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 16:13:29 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 16:14:22 (3867) [[32mINFO[0m] http://103.252.152.1/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno 12] Timeout on http://103.252.152.1/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 16:14:22 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 16:15:02 (3867) [[32mINFO[0m] http://45.234.92.141/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno 12] Timeout on http://45.234.92.141/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 16:15:02 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 16:15:42 (3867) [[32mINFO[0m] http://103.15.48.49/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno 12] Timeout on http://103.15.48.49/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 16:15:42 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 16:16:04 (3867) [[32mINFO[0m] http://103.72.162.35/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-04-28 16:16:04 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 16:17:21 (3867) [[32mINFO[0m] http://185.15.22.168/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno 12] Timeout on http://185.15.22.168/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-04-28 16:17:21 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 16:17:33 (3867) [[32mINFO[0m] http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/85cce9a1c3820c936ee8f2dd3e822be4bba0d2a2abbe3a3e278adc4d6df50875-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-04-28 16:17:33 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-04-28 16:18:13 (3867) [[32mINFO[0m] 
* 2023-04-28 16:18:13 (3867) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-28 16:18:13 (3884) [[32mINFO[0m] 
* 2023-04-28 16:18:13 (1580) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-28 16:18:13 (144) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-28 16:20:13 (1439) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-04-28 16:20:13 (1440) [[31mERROR[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/6031e4bbc0be206e229f60814365e6488e61f97d7e6da3d03698c41f1369b37e-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://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/dcdaa2581dc3feb4877b6352da6b96ad08098d55710aff024eacd643df4940de-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
* 2023-04-28 16:20:13 (144) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-28 16:20:13 (681) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-28 16:20:13 (2015) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/y_9Z9XStbJ/ea_profile.json
* 2023-04-28 16:20:15 (2038) [[32mINFO[0m] Backed up EA4 profile to /tmp/y_9Z9XStbJ/ea_profile.json
* 2023-04-28 16:20:17 (244) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-29 02:13:00 (1573) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-29 02:13:00 (3853) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-29 02:13:00 (3854) [[32mINFO[0m] 
* 2023-04-29 02:13:00 (3867) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-29 02:13:00 (3867) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-29 02:13:00 (3867) [[32mINFO[0m]               : epel extras updates
* 2023-04-29 02:13:00 (3867) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-29 02:13:00 (3884) [[32mINFO[0m] 
* 2023-04-29 02:13:00 (3853) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-29 02:13:00 (3854) [[32mINFO[0m] 
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m] 14: curl#52 - "Empty reply from server"
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m] 
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m] 
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m] 
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m] 
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m] 
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m] 
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m] 
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]         or
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m] 
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]         compromise:
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m] 
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m] 
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m] Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2023-04-29 02:13:10 (3884) [[32mINFO[0m] 
* 2023-04-29 02:13:10 (1580) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-29 02:13:10 (1594) [[32mINFO[0m] Checking /scripts/sysup
* 2023-04-29 02:13:10 (3853) [[32mINFO[0m] Running: /scripts/sysup
* 2023-04-29 02:13:10 (3854) [[32mINFO[0m] 
* 2023-04-29 02:13:10 (3867) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-04-29 02:13:11 (3867) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-04-29 02:13:11 (3884) [[32mINFO[0m] 
* 2023-04-29 02:16:05 (1439) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-04-29 02:16:05 (1440) [[31mERROR[0m] http://mirror.radoreservers.com/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.radoreservers.com/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://162.252.87.234/cpanelsync/repos/CentOS/7/EA4/repodata/784ac6932457aa56b27f33c3e06fa1365bba3aada172b118d61c11ff1783a6f5-filelists.sqlite.bz2: [Errno 12] Timeout on http://162.252.87.234/cpanelsync/repos/CentOS/7/EA4/repodata/784ac6932457aa56b27f33c3e06fa1365bba3aada172b118d61c11ff1783a6f5-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/784ac6932457aa56b27f33c3e06fa1365bba3aada172b118d61c11ff1783a6f5-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/784ac6932457aa56b27f33c3e06fa1365bba3aada172b118d61c11ff1783a6f5-filelists.sqlite.bz2: [Errno 12] Timeout on http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/784ac6932457aa56b27f33c3e06fa1365bba3aada172b118d61c11ff1783a6f5-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.74.123.61/cpanelsync/repos/CentOS/7/EA4/repodata/784ac6932457aa56b27f33c3e06fa1365bba3aada172b118d61c11ff1783a6f5-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-04-29 02:16:05 (144) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-29 02:16:05 (681) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-29 02:16:05 (2015) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YlfUs3oN4d/ea_profile.json
* 2023-04-29 02:16:07 (2038) [[32mINFO[0m] Backed up EA4 profile to /tmp/YlfUs3oN4d/ea_profile.json
* 2023-04-29 02:16:08 (244) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-04-30 02:19:23 (1573) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-04-30 02:19:23 (3853) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-04-30 02:19:23 (3854) [[32mINFO[0m] 
* 2023-04-30 02:19:24 (3867) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-30 02:19:24 (3867) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-04-30 02:19:24 (3867) [[32mINFO[0m]               : epel extras updates
* 2023-04-30 02:19:24 (3867) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-04-30 02:19:24 (3884) [[32mINFO[0m] 
* 2023-04-30 02:19:24 (3853) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-04-30 02:19:24 (3854) [[32mINFO[0m] 
* 2023-04-30 02:20:14 (3867) [[32mINFO[0m] 
* 2023-04-30 02:20:14 (3867) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-30 02:20:14 (3884) [[32mINFO[0m] 
* 2023-04-30 02:20:14 (1580) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-30 02:20:14 (144) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-30 02:23:01 (1439) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-04-30 02:23:01 (1440) [[31mERROR[0m] http://mirror.bursabil.com.tr/centos/7.9.2009/updates/x86_64/repodata/14fe00ffab4acf4dca4c082f52d89927fbc56d6d3e0e8961d37b138609ba07e8-filelists.sqlite.bz2: [Errno 12] Timeout on http://mirror.bursabil.com.tr/centos/7.9.2009/updates/x86_64/repodata/14fe00ffab4acf4dca4c082f52d89927fbc56d6d3e0e8961d37b138609ba07e8-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirror.bursabil.com.tr/centos/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on http://mirror.bursabil.com.tr/centos/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
* 2023-04-30 02:23:01 (144) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-30 02:23:01 (681) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-30 02:23:01 (2015) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tzED6HEtRf/ea_profile.json
* 2023-04-30 02:23:03 (2038) [[32mINFO[0m] Backed up EA4 profile to /tmp/tzED6HEtRf/ea_profile.json
* 2023-04-30 02:23:04 (244) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-01 02:15:28 (1573) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-01 02:15:28 (3853) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-01 02:15:28 (3854) [[32mINFO[0m] 
* 2023-05-01 02:15:28 (3867) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-01 02:15:28 (3867) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-01 02:15:28 (3867) [[32mINFO[0m]               : epel extras updates
* 2023-05-01 02:15:29 (3867) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-01 02:15:29 (3884) [[32mINFO[0m] 
* 2023-05-01 02:15:29 (3853) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-01 02:15:29 (3854) [[32mINFO[0m] 
* 2023-05-01 02:16:27 (3867) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/0dc033a93996fba0f25e37ac6981a30807216385c5ff4567563741f248aea971-primary.sqlite.bz2: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/0dc033a93996fba0f25e37ac6981a30807216385c5ff4567563741f248aea971-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-01 02:16:27 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-05-01 02:16:29 (3867) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/0dc033a93996fba0f25e37ac6981a30807216385c5ff4567563741f248aea971-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-05-01 02:16:29 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-05-01 02:16:29 (3867) [[32mINFO[0m] To address this issue please refer to the below wiki article 
* 2023-05-01 02:16:29 (3867) [[32mINFO[0m] 
* 2023-05-01 02:16:29 (3867) [[32mINFO[0m] https://wiki.centos.org/yum-errors
* 2023-05-01 02:16:29 (3867) [[32mINFO[0m] 
* 2023-05-01 02:16:29 (3867) [[32mINFO[0m] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2023-05-01 02:16:29 (3867) [[32mINFO[0m] 
* 2023-05-01 02:17:15 (3867) [[32mINFO[0m] https://epel.excellmedia.net/7/x86_64/repodata/0dc033a93996fba0f25e37ac6981a30807216385c5ff4567563741f248aea971-primary.sqlite.bz2: [Errno 12] Timeout on https://epel.excellmedia.net/7/x86_64/repodata/0dc033a93996fba0f25e37ac6981a30807216385c5ff4567563741f248aea971-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-01 02:17:15 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-05-01 02:17:37 (3867) [[32mINFO[0m] 
* 2023-05-01 02:17:37 (3867) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-05-01 02:17:37 (3884) [[32mINFO[0m] 
* 2023-05-01 02:17:37 (1580) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-01 02:17:37 (144) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-01 02:20:18 (681) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-01 02:20:18 (2015) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hMyqGbZFpN/ea_profile.json
* 2023-05-01 02:20:19 (2038) [[32mINFO[0m] Backed up EA4 profile to /tmp/hMyqGbZFpN/ea_profile.json
* 2023-05-01 02:20:21 (244) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-02 02:12:58 (1573) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-02 02:12:58 (3853) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-02 02:12:58 (3854) [[32mINFO[0m] 
* 2023-05-02 02:12:58 (3867) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-02 02:12:58 (3867) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-02 02:12:58 (3867) [[32mINFO[0m]               : epel extras updates
* 2023-05-02 02:12:58 (3867) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-02 02:12:58 (3884) [[32mINFO[0m] 
* 2023-05-02 02:12:58 (3853) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-02 02:12:58 (3854) [[32mINFO[0m] 
* 2023-05-02 02:13:56 (3867) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-02 02:13:56 (3867) [[32mINFO[0m] Trying other mirror.
* 2023-05-02 02:18:03 (3867) [[32mINFO[0m] 
* 2023-05-02 02:18:03 (3867) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-05-02 02:18:03 (3884) [[32mINFO[0m] 
* 2023-05-02 02:18:03 (1580) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-02 02:18:03 (144) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-02 02:18:37 (681) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-02 02:18:37 (2015) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/78pQtjn76I/ea_profile.json
* 2023-05-02 02:18:38 (2038) [[32mINFO[0m] Backed up EA4 profile to /tmp/78pQtjn76I/ea_profile.json
* 2023-05-02 02:18:40 (244) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-03 02:14:42 (1573) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-03 02:14:42 (3853) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-03 02:14:42 (3854) [[32mINFO[0m] 
* 2023-05-03 02:14:42 (3867) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-03 02:14:42 (3867) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-03 02:14:42 (3867) [[32mINFO[0m]               : epel extras updates
* 2023-05-03 02:14:42 (3867) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-03 02:14:42 (3884) [[32mINFO[0m] 
* 2023-05-03 02:14:42 (3853) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-03 02:14:42 (3854) [[32mINFO[0m] 
* 2023-05-03 02:15:33 (3867) [[32mINFO[0m] 
* 2023-05-03 02:15:33 (3867) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-05-03 02:15:33 (3884) [[32mINFO[0m] 
* 2023-05-03 02:15:33 (1580) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-03 02:15:33 (144) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-03 02:17:17 (1439) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-05-03 02:17:17 (1440) [[31mERROR[0m] http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/repomd.xml: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
https://mirror.yer.az/fedora-epel/7/x86_64/repodata/654409dc953044b2fbd2992d9981b20528caedbe2cd8a24141361351ab9fc12a-filelists.sqlite.bz2: [Errno 12] Timeout on https://mirror.yer.az/fedora-epel/7/x86_64/repodata/654409dc953044b2fbd2992d9981b20528caedbe2cd8a24141361351ab9fc12a-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
* 2023-05-03 02:17:17 (144) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-03 02:17:17 (681) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-03 02:17:17 (2015) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NvSXPlr8Ue/ea_profile.json
* 2023-05-03 02:17:19 (2038) [[32mINFO[0m] Backed up EA4 profile to /tmp/NvSXPlr8Ue/ea_profile.json
* 2023-05-03 02:17:20 (244) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-04 02:18:41 (1625) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-04 02:18:41 (3905) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-04 02:18:41 (3906) [[32mINFO[0m] 
* 2023-05-04 02:18:41 (3919) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-04 02:18:41 (3919) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-04 02:18:41 (3919) [[32mINFO[0m]               : epel extras updates
* 2023-05-04 02:18:42 (3919) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-04 02:18:42 (3936) [[32mINFO[0m] 
* 2023-05-04 02:18:42 (3905) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-04 02:18:42 (3906) [[32mINFO[0m] 
* 2023-05-04 02:19:23 (3919) [[32mINFO[0m] 
* 2023-05-04 02:19:23 (3919) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-05-04 02:19:23 (3936) [[32mINFO[0m] 
* 2023-05-04 02:19:23 (1632) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-04 02:19:23 (145) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-04 02:19:50 (734) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-04 02:19:50 (2067) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jBienzDwxs/ea_profile.json
* 2023-05-04 02:19:52 (2090) [[32mINFO[0m] Backed up EA4 profile to /tmp/jBienzDwxs/ea_profile.json
* 2023-05-04 02:19:55 (246) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-05 02:24:29 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-05-05 02:24:30 (1625) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-05 02:24:30 (3905) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-05 02:24:30 (3906) [[32mINFO[0m] 
* 2023-05-05 02:24:31 (3919) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-05 02:24:31 (3919) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-05 02:24:31 (3919) [[32mINFO[0m]               : epel extras updates
* 2023-05-05 02:24:32 (3919) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-05 02:24:32 (3936) [[32mINFO[0m] 
* 2023-05-05 02:24:32 (3905) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-05 02:24:32 (3906) [[32mINFO[0m] 
* 2023-05-05 02:25:11 (3919) [[32mINFO[0m] http://mirror.verinomi.com/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://mirror.verinomi.com/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
* 2023-05-05 02:25:32 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-05 02:26:24 (3919) [[32mINFO[0m] http://mirror.earthlink.iq/epel/7/x86_64/repodata/c68cd1dcfc023bf1f38b1016c4efb821d85fc3cca7b33f3e9ded9de4cd4f566c-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.earthlink.iq/epel/7/x86_64/repodata/c68cd1dcfc023bf1f38b1016c4efb821d85fc3cca7b33f3e9ded9de4cd4f566c-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-05 02:26:24 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-05 02:26:47 (3919) [[32mINFO[0m] 
* 2023-05-05 02:26:47 (3919) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-05-05 02:26:47 (3936) [[32mINFO[0m] 
* 2023-05-05 02:26:47 (1632) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-05 02:26:47 (145) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-05 02:27:16 (734) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-05 02:27:16 (2067) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_wDFxvGvAN/ea_profile.json
* 2023-05-05 02:27:17 (2090) [[32mINFO[0m] Backed up EA4 profile to /tmp/_wDFxvGvAN/ea_profile.json
* 2023-05-05 02:27:20 (246) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-05 15:53:42 (1625) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-05 15:53:42 (3905) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-05 15:53:42 (3906) [[32mINFO[0m] 
* 2023-05-05 15:53:42 (3919) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-05 15:53:42 (3919) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-05 15:53:42 (3919) [[32mINFO[0m]               : epel extras updates
* 2023-05-05 15:53:43 (3919) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-05 15:53:43 (3936) [[32mINFO[0m] 
* 2023-05-05 15:53:43 (3905) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-05 15:53:43 (3906) [[32mINFO[0m] 
* 2023-05-05 15:54:37 (3919) [[32mINFO[0m] http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: [Errno 12] Timeout on http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-05 15:54:37 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-05 15:55:35 (3919) [[32mINFO[0m] http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: [Errno 12] Timeout on http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-05 15:55:35 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-05 15:55:40 (3919) [[32mINFO[0m] http://208.74.123.61/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-05-05 15:55:40 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-05 15:57:15 (3919) [[32mINFO[0m] http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: [Errno 12] Timeout on http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-05 15:57:15 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-05 15:57:19 (3919) [[32mINFO[0m] http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-05-05 15:57:19 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-05 15:57:41 (3919) [[32mINFO[0m] 
* 2023-05-05 15:57:41 (3919) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-05 15:57:41 (3936) [[32mINFO[0m] 
* 2023-05-05 15:57:41 (1632) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-05 15:57:41 (145) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-05 16:04:23 (1491) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-05-05 16:04:23 (1492) [[31mERROR[0m] http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/1d560480c71de112e777bac0f4ffed221e8650ff8f0892be24df1cca52bf8696-filelists.sqlite.bz2: [Errno 12] Timeout on http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/1d560480c71de112e777bac0f4ffed221e8650ff8f0892be24df1cca52bf8696-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/78c1c30d5863c3daaa3e1ce44ea529d376b42c51650d8836a5affa3422107acd-filelists.sqlite.bz2: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/78c1c30d5863c3daaa3e1ce44ea529d376b42c51650d8836a5affa3422107acd-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/1d560480c71de112e777bac0f4ffed221e8650ff8f0892be24df1cca52bf8696-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/1d560480c71de112e777bac0f4ffed221e8650ff8f0892be24df1cca52bf8696-filelists.sqlite.bz2: [Errno 12] Timeout on http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/1d560480c71de112e777bac0f4ffed221e8650ff8f0892be24df1cca52bf8696-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/1d560480c71de112e777bac0f4ffed221e8650ff8f0892be24df1cca52bf8696-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-05-05 16:04:23 (145) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-05 16:04:23 (734) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-05 16:04:23 (2067) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RAwmwd3H5q/ea_profile.json
* 2023-05-05 16:04:25 (2090) [[32mINFO[0m] Backed up EA4 profile to /tmp/RAwmwd3H5q/ea_profile.json
* 2023-05-05 16:04:28 (246) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-06 02:20:58 (1625) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-06 02:20:58 (3905) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-06 02:20:58 (3906) [[32mINFO[0m] 
* 2023-05-06 02:20:58 (3919) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-06 02:20:58 (3919) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-06 02:20:58 (3919) [[32mINFO[0m]               : epel extras updates
* 2023-05-06 02:20:58 (3919) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-06 02:20:58 (3936) [[32mINFO[0m] 
* 2023-05-06 02:20:58 (3905) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-06 02:20:58 (3906) [[32mINFO[0m] 
* 2023-05-06 02:21:42 (3919) [[32mINFO[0m] 
* 2023-05-06 02:21:42 (3919) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-06 02:21:42 (3936) [[32mINFO[0m] 
* 2023-05-06 02:21:42 (1632) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-06 02:21:42 (145) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-06 02:24:08 (734) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-06 02:24:08 (2067) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4tfaHTAibu/ea_profile.json
* 2023-05-06 02:24:09 (2090) [[32mINFO[0m] Backed up EA4 profile to /tmp/4tfaHTAibu/ea_profile.json
* 2023-05-06 02:24:12 (246) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-07 00:04:18 (1625) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-07 00:04:18 (3905) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-07 00:04:18 (3906) [[32mINFO[0m] 
* 2023-05-07 00:04:19 (3919) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-07 00:04:19 (3919) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-07 00:04:19 (3919) [[32mINFO[0m]               : epel extras updates
* 2023-05-07 00:04:19 (3919) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-07 00:04:19 (3936) [[32mINFO[0m] 
* 2023-05-07 00:04:19 (3905) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-07 00:04:19 (3906) [[32mINFO[0m] 
* 2023-05-07 00:06:07 (3919) [[32mINFO[0m] http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: [Errno 12] Timeout on http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-07 00:06:07 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 00:06:43 (3919) [[32mINFO[0m] http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: [Errno 12] Timeout on http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-07 00:06:43 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 00:08:01 (3919) [[32mINFO[0m] http://103.101.161.235/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: [Errno 12] Timeout on http://103.101.161.235/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-07 00:08:01 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 00:08:52 (3919) [[32mINFO[0m] http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-07 00:08:52 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 00:10:28 (3919) [[32mINFO[0m] http://102.22.80.80/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: [Errno 12] Timeout on http://102.22.80.80/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-07 00:10:28 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 00:11:26 (3919) [[32mINFO[0m] http://istanbul.centos-mirror.guzel.net.tr/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-05-07 00:11:26 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 00:11:50 (3919) [[32mINFO[0m] http://103.120.66.133/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: [Errno 12] Timeout on http://103.120.66.133/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-07 00:11:50 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 00:12:25 (3919) [[32mINFO[0m] http://mirror.earthlink.iq/centos/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.earthlink.iq/centos/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-07 00:12:25 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 00:13:17 (3919) [[32mINFO[0m] http://118.88.24.67/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: [Errno 12] Timeout on http://118.88.24.67/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-07 00:13:18 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 00:15:09 (3919) [[32mINFO[0m] http://184.94.196.97/cpanelsync/repos/CentOS/7/EA4/repodata/41324a05ab51d6c8ad647fb77ca67489e3d926bef7740ba13e738b0efc88c7e0-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-05-07 00:15:09 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 00:20:53 (3919) [[32mINFO[0m] http://repo.boun.edu.tr/centos/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-05-07 00:20:53 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 00:21:59 (3919) [[32mINFO[0m] http://mirror.onlinehosting.com.tr/centos/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.onlinehosting.com.tr/centos/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-07 00:21:59 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 00:22:37 (3919) [[32mINFO[0m] http://mirror.natro.com/centos/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.natro.com/centos/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-07 00:22:37 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 00:22:41 (3919) [[32mINFO[0m] http://centos.vargonen.com/centos/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
* 2023-05-07 00:22:41 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 00:23:18 (3919) [[32mINFO[0m] http://centos.turhost.com/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: [Errno 12] Timeout on http://centos.turhost.com/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-07 00:23:18 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 00:24:13 (3919) [[32mINFO[0m] http://mirror.netdirekt.com.tr/centos/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.netdirekt.com.tr/centos/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-07 00:24:13 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 00:25:43 (3919) [[32mINFO[0m] http://mirror.centos.jt.iq/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.centos.jt.iq/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-07 00:25:43 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 00:26:13 (3919) [[32mINFO[0m] http://mirror.verinomi.com/centos/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.verinomi.com/centos/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds')
* 2023-05-07 00:26:13 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 00:31:50 (3919) [[32mINFO[0m] http://istanbul.centos-mirror.guzel.net.tr/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-05-07 00:31:50 (3919) [[32mINFO[0m] Trying other mirror.
* 2023-05-07 02:18:36 (1625) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-07 02:18:36 (3905) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-07 02:18:36 (3906) [[32mINFO[0m] 
* 2023-05-07 02:18:37 (3919) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-07 02:18:37 (3919) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-07 02:18:37 (3919) [[32mINFO[0m]               : epel extras updates
* 2023-05-07 02:18:37 (3919) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-07 02:18:37 (3936) [[32mINFO[0m] 
* 2023-05-07 02:18:37 (3905) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-07 02:18:37 (3906) [[32mINFO[0m] 
* 2023-05-07 02:19:37 (3936) [[32mINFO[0m] 
* 2023-05-07 02:19:37 (1646) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-07 02:19:37 (3905) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-07 02:19:37 (3906) [[32mINFO[0m] 
* 2023-05-07 02:19:37 (3919) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-07 02:19:39 (3919) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-07 02:19:39 (3936) [[32mINFO[0m] 
* 2023-05-07 02:23:17 (1491) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-05-07 02:23:17 (1492) [[31mERROR[0m] http://mirror.earthlink.iq/centos/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on http://mirror.earthlink.iq/centos/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
* 2023-05-07 02:23:17 (145) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-07 02:23:17 (734) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-07 02:23:17 (2067) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XlHS505xWg/ea_profile.json
* 2023-05-07 02:23:18 (2090) [[32mINFO[0m] Backed up EA4 profile to /tmp/XlHS505xWg/ea_profile.json
* 2023-05-07 02:23:21 (145) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.83.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.90.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-05-07 02:23:22 (246) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-07 09:44:32 (1625) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-07 09:44:32 (3905) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-07 09:44:32 (3906) [[32mINFO[0m] 
* 2023-05-07 09:44:32 (3919) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-07 09:44:32 (3919) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-07 09:44:32 (3919) [[32mINFO[0m]               : epel extras updates
* 2023-05-07 09:44:33 (3919) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-07 09:44:33 (3936) [[32mINFO[0m] 
* 2023-05-07 09:44:33 (3905) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-07 09:44:33 (3906) [[32mINFO[0m] 
* 2023-05-07 09:45:04 (3936) [[32mINFO[0m] 
* 2023-05-07 09:45:04 (1646) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-07 09:45:04 (3905) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-07 09:45:04 (3906) [[32mINFO[0m] 
* 2023-05-07 09:45:05 (3919) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-07 09:45:06 (3919) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-07 09:45:06 (3936) [[32mINFO[0m] 
* 2023-05-07 09:47:26 (1491) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-05-07 09:47:26 (1492) [[31mERROR[0m] http://184.94.196.92/cpanelsync/repos/CentOS/7/EA4/repodata/1d560480c71de112e777bac0f4ffed221e8650ff8f0892be24df1cca52bf8696-filelists.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.92/cpanelsync/repos/CentOS/7/EA4/repodata/1d560480c71de112e777bac0f4ffed221e8650ff8f0892be24df1cca52bf8696-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.92/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/04f2a20275eedd4f5f066595c531787146707a1df08b92d7b9265408474733db-filelists.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.92/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/04f2a20275eedd4f5f066595c531787146707a1df08b92d7b9265408474733db-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.92/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/d813c27fae98618fbbba4e613c3ee0f1b341074ee8670428abdf8fb6a6f3535b-filelists.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.92/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/d813c27fae98618fbbba4e613c3ee0f1b341074ee8670428abdf8fb6a6f3535b-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://184.94.196.94/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/04f2a20275eedd4f5f066595c531787146707a1df08b92d7b9265408474733db-filelists.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.94/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/04f2a20275eedd4f5f066595c531787146707a1df08b92d7b9265408474733db-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://185.157.208.252/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/04f2a20275eedd4f5f066595c531787146707a1df08b92d7b9265408474733db-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://184.94.196.94/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/d813c27fae98618fbbba4e613c3ee0f1b341074ee8670428abdf8fb6a6f3535b-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://184.94.196.94/cpanelsync/repos/CentOS/7/EA4/repodata/1d560480c71de112e777bac0f4ffed221e8650ff8f0892be24df1cca52bf8696-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://185.157.208.252/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/d813c27fae98618fbbba4e613c3ee0f1b341074ee8670428abdf8fb6a6f3535b-filelists.sqlite.bz2: [Errno 12] Timeout on http://185.157.208.252/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/d813c27fae98618fbbba4e613c3ee0f1b341074ee8670428abdf8fb6a6f3535b-filelists.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
* 2023-05-07 09:47:26 (145) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-07 09:47:27 (734) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-07 09:47:27 (2067) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sUjqQ54CUa/ea_profile.json
* 2023-05-07 09:47:28 (2090) [[32mINFO[0m] Backed up EA4 profile to /tmp/sUjqQ54CUa/ea_profile.json
* 2023-05-07 09:47:30 (145) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.83.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.90.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-05-07 09:47:31 (246) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-08 02:19:02 (1625) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-08 02:19:02 (3905) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-08 02:19:02 (3906) [[32mINFO[0m] 
* 2023-05-08 02:19:02 (3919) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-08 02:19:02 (3919) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-08 02:19:02 (3919) [[32mINFO[0m]               : epel extras updates
* 2023-05-08 02:19:02 (3919) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-08 02:19:02 (3936) [[32mINFO[0m] 
* 2023-05-08 02:19:02 (3905) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-08 02:19:02 (3906) [[32mINFO[0m] 
* 2023-05-08 02:19:44 (3936) [[32mINFO[0m] 
* 2023-05-08 02:19:44 (1646) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-08 02:19:44 (3905) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-08 02:19:44 (3906) [[32mINFO[0m] 
* 2023-05-08 02:19:44 (3919) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-08 02:19:45 (3919) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-08 02:19:45 (3936) [[32mINFO[0m] 
* 2023-05-08 02:20:52 (734) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-08 02:20:52 (2067) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bs9Q40gFRO/ea_profile.json
* 2023-05-08 02:20:53 (2090) [[32mINFO[0m] Backed up EA4 profile to /tmp/bs9Q40gFRO/ea_profile.json
* 2023-05-08 02:20:55 (145) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.83.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.90.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-05-08 02:20:56 (246) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-09 02:15:36 (1659) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-09 02:15:36 (3974) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-09 02:15:36 (3975) [[32mINFO[0m] 
* 2023-05-09 02:15:37 (3988) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-09 02:15:37 (3988) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-09 02:15:37 (3988) [[32mINFO[0m]               : epel extras updates
* 2023-05-09 02:15:37 (3988) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-09 02:15:37 (4005) [[32mINFO[0m] 
* 2023-05-09 02:15:37 (3974) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-09 02:15:37 (3975) [[32mINFO[0m] 
* 2023-05-09 02:16:26 (4005) [[32mINFO[0m] 
* 2023-05-09 02:16:26 (1680) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-09 02:16:26 (3974) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-09 02:16:26 (3975) [[32mINFO[0m] 
* 2023-05-09 02:16:26 (3988) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-09 02:16:27 (3988) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-09 02:16:27 (4005) [[32mINFO[0m] 
* 2023-05-09 02:17:58 (741) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-09 02:17:58 (2136) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PddGGOejUD/ea_profile.json
* 2023-05-09 02:17:59 (2159) [[32mINFO[0m] Backed up EA4 profile to /tmp/PddGGOejUD/ea_profile.json
* 2023-05-09 02:18:02 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.83.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.90.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-05-09 02:18:03 (251) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-10 02:22:42 (1659) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-10 02:22:42 (3974) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-10 02:22:42 (3975) [[32mINFO[0m] 
* 2023-05-10 02:22:42 (3988) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-10 02:22:42 (3988) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-10 02:22:42 (3988) [[32mINFO[0m]               : epel extras updates
* 2023-05-10 02:22:43 (3988) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-10 02:22:43 (4005) [[32mINFO[0m] 
* 2023-05-10 02:22:43 (3974) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-10 02:22:43 (3975) [[32mINFO[0m] 
* 2023-05-10 02:24:03 (3988) [[32mINFO[0m] http://mirror.onlinehosting.com.tr/centos/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.onlinehosting.com.tr/centos/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-10 02:24:03 (3988) [[32mINFO[0m] Trying other mirror.
* 2023-05-10 02:24:54 (4005) [[32mINFO[0m] 
* 2023-05-10 02:24:54 (1680) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-10 02:24:54 (3974) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-10 02:24:54 (3975) [[32mINFO[0m] 
* 2023-05-10 02:24:54 (3988) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-10 02:24:56 (3988) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-10 02:24:56 (4005) [[32mINFO[0m] 
* 2023-05-10 02:28:28 (1525) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-05-10 02:28:28 (1526) [[31mERROR[0m] http://mirror.radoreservers.com/centos/7.9.2009/updates/x86_64/repodata/553ee4a1428f4d8208841ff88ed15a72dca0e16b251762875a08233c304b3dba-filelists.sqlite.bz2: [Errno 12] Timeout on http://mirror.radoreservers.com/centos/7.9.2009/updates/x86_64/repodata/553ee4a1428f4d8208841ff88ed15a72dca0e16b251762875a08233c304b3dba-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://185.157.208.252/cpanelsync/repos/CentOS/7/EA4/repodata/1d560480c71de112e777bac0f4ffed221e8650ff8f0892be24df1cca52bf8696-filelists.sqlite.bz2: [Errno 12] Timeout on http://185.157.208.252/cpanelsync/repos/CentOS/7/EA4/repodata/1d560480c71de112e777bac0f4ffed221e8650ff8f0892be24df1cca52bf8696-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/1d560480c71de112e777bac0f4ffed221e8650ff8f0892be24df1cca52bf8696-filelists.sqlite.bz2: [Errno 12] Timeout on http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/1d560480c71de112e777bac0f4ffed221e8650ff8f0892be24df1cca52bf8696-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://103.48.119.120/cpanelsync/repos/CentOS/7/EA4/repodata/1d560480c71de112e777bac0f4ffed221e8650ff8f0892be24df1cca52bf8696-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-05-10 02:28:28 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-10 02:28:28 (741) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-10 02:28:30 (2136) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ys7ZiTqhzo/ea_profile.json
* 2023-05-10 02:28:31 (2159) [[32mINFO[0m] Backed up EA4 profile to /tmp/ys7ZiTqhzo/ea_profile.json
* 2023-05-10 02:28:33 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.83.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.90.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-05-10 02:28:34 (251) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-11 02:28:38 (1659) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-11 02:28:38 (3974) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-11 02:28:38 (3975) [[32mINFO[0m] 
* 2023-05-11 02:28:39 (3988) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-11 02:28:39 (3988) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-11 02:28:39 (3988) [[32mINFO[0m]               : epel extras updates
* 2023-05-11 02:28:39 (3988) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-11 02:28:39 (4005) [[32mINFO[0m] 
* 2023-05-11 02:28:39 (3974) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-11 02:28:39 (3975) [[32mINFO[0m] 
* 2023-05-11 02:29:22 (4005) [[32mINFO[0m] 
* 2023-05-11 02:29:22 (1680) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-11 02:29:22 (3974) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-11 02:29:22 (3975) [[32mINFO[0m] 
* 2023-05-11 02:29:24 (3988) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-11 02:29:25 (3988) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-11 02:29:25 (4005) [[32mINFO[0m] 
* 2023-05-11 02:30:21 (741) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-11 02:30:21 (2136) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KjhErq1AWV/ea_profile.json
* 2023-05-11 02:30:22 (2159) [[32mINFO[0m] Backed up EA4 profile to /tmp/KjhErq1AWV/ea_profile.json
* 2023-05-11 02:30:24 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.83.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.90.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-05-11 02:30:25 (251) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-12 02:15:17 (1659) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-12 02:15:17 (3974) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-12 02:15:17 (3975) [[32mINFO[0m] 
* 2023-05-12 02:15:18 (3988) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-12 02:15:18 (3988) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-12 02:15:18 (3988) [[32mINFO[0m]               : epel extras updates
* 2023-05-12 02:15:18 (3988) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-12 02:15:18 (4005) [[32mINFO[0m] 
* 2023-05-12 02:15:18 (3974) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-12 02:15:18 (3975) [[32mINFO[0m] 
* 2023-05-12 02:16:38 (4005) [[32mINFO[0m] 
* 2023-05-12 02:16:38 (1680) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-12 02:16:38 (3974) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-12 02:16:38 (3975) [[32mINFO[0m] 
* 2023-05-12 02:16:38 (3988) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-12 02:16:39 (3988) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-12 02:16:39 (4005) [[32mINFO[0m] 
* 2023-05-12 02:18:30 (1525) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-05-12 02:18:30 (1526) [[31mERROR[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/f0c59304db467f5a1cea4cf4bc1f0e2aad3d7bb30ea9447c41e54b153225e91e-filelists.sqlite.bz2: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/f0c59304db467f5a1cea4cf4bc1f0e2aad3d7bb30ea9447c41e54b153225e91e-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
* 2023-05-12 02:18:30 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-12 02:18:31 (741) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-12 02:18:32 (2136) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YR8gZqx2xq/ea_profile.json
* 2023-05-12 02:18:34 (2159) [[32mINFO[0m] Backed up EA4 profile to /tmp/YR8gZqx2xq/ea_profile.json
* 2023-05-12 02:18:36 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.83.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.90.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-05-12 02:18:37 (251) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-13 02:18:25 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
disk space issue
* 2023-05-13 02:18:27 (1659) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-13 02:18:27 (3974) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-13 02:18:27 (3975) [[32mINFO[0m] 
* 2023-05-13 02:18:27 (3988) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-13 02:18:27 (3988) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-13 02:18:27 (3988) [[32mINFO[0m]               : epel extras updates
* 2023-05-13 02:18:27 (3988) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-13 02:18:27 (4005) [[32mINFO[0m] 
* 2023-05-13 02:18:27 (3974) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-13 02:18:27 (3975) [[32mINFO[0m] 
* 2023-05-13 02:19:13 (3988) [[32mINFO[0m] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/aa7587f230672911243a35c83286a1b7f9dd74b97684795cc5e60779b8ec90da-primary.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/aa7587f230672911243a35c83286a1b7f9dd74b97684795cc5e60779b8ec90da-primary.sqlite.bz2: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
* 2023-05-13 02:19:13 (3988) [[32mINFO[0m] Trying other mirror.
* 2023-05-13 02:19:42 (4005) [[32mINFO[0m] 
* 2023-05-13 02:19:42 (1680) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-13 02:19:42 (3974) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-13 02:19:42 (3975) [[32mINFO[0m] 
* 2023-05-13 02:19:42 (3988) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-13 02:19:43 (3988) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-13 02:19:43 (4005) [[32mINFO[0m] 
* 2023-05-13 02:20:38 (1525) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-05-13 02:20:38 (1526) [[31mERROR[0m] http://208.100.0.204/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/04f2a20275eedd4f5f066595c531787146707a1df08b92d7b9265408474733db-filelists.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
http://208.100.0.204/cpanelsync/repos/CentOS/7/EA4/repodata/e82b97eebdbc9fc7c84f19092764a4dcb377ebd430a66d6dea77f3fa064cf8e1-filelists.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
* 2023-05-13 02:20:38 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-13 02:20:38 (741) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-13 02:20:38 (2136) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bbkM9B7bwz/ea_profile.json
* 2023-05-13 02:20:40 (2159) [[32mINFO[0m] Backed up EA4 profile to /tmp/bbkM9B7bwz/ea_profile.json
* 2023-05-13 02:20:42 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.83.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.90.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-05-13 02:20:43 (251) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-13 13:22:12 (1659) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-13 13:22:12 (3974) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-13 13:22:12 (3975) [[32mINFO[0m] 
* 2023-05-13 13:22:12 (3988) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-13 13:22:13 (3988) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-13 13:22:13 (3988) [[32mINFO[0m]               : epel extras updates
* 2023-05-13 13:22:13 (3988) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-13 13:22:13 (4005) [[32mINFO[0m] 
* 2023-05-13 13:22:13 (3974) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-13 13:22:13 (3975) [[32mINFO[0m] 
* 2023-05-13 13:23:09 (3988) [[32mINFO[0m] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/aa7587f230672911243a35c83286a1b7f9dd74b97684795cc5e60779b8ec90da-primary.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/aa7587f230672911243a35c83286a1b7f9dd74b97684795cc5e60779b8ec90da-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-13 13:23:09 (3988) [[32mINFO[0m] Trying other mirror.
* 2023-05-13 13:24:07 (3988) [[32mINFO[0m] http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/2d8d438782e1bf0437738d9bf0761e02fa4c55ff76a87162a0342ce1af899c92-primary.sqlite.bz2: [Errno 12] Timeout on http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/2d8d438782e1bf0437738d9bf0761e02fa4c55ff76a87162a0342ce1af899c92-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-13 13:24:07 (3988) [[32mINFO[0m] Trying other mirror.
* 2023-05-13 13:24:45 (3988) [[32mINFO[0m] http://208.74.123.61/cpanelsync/repos/CentOS/7/EA4/repodata/2d8d438782e1bf0437738d9bf0761e02fa4c55ff76a87162a0342ce1af899c92-primary.sqlite.bz2: [Errno 12] Timeout on http://208.74.123.61/cpanelsync/repos/CentOS/7/EA4/repodata/2d8d438782e1bf0437738d9bf0761e02fa4c55ff76a87162a0342ce1af899c92-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-13 13:24:45 (3988) [[32mINFO[0m] Trying other mirror.
* 2023-05-13 13:25:59 (3988) [[32mINFO[0m] http://103.15.48.49/cpanelsync/repos/CentOS/7/EA4/repodata/2d8d438782e1bf0437738d9bf0761e02fa4c55ff76a87162a0342ce1af899c92-primary.sqlite.bz2: [Errno 12] Timeout on http://103.15.48.49/cpanelsync/repos/CentOS/7/EA4/repodata/2d8d438782e1bf0437738d9bf0761e02fa4c55ff76a87162a0342ce1af899c92-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-13 13:25:59 (3988) [[32mINFO[0m] Trying other mirror.
* 2023-05-13 13:26:36 (3988) [[32mINFO[0m] http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/2d8d438782e1bf0437738d9bf0761e02fa4c55ff76a87162a0342ce1af899c92-primary.sqlite.bz2: [Errno 12] Timeout on http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/2d8d438782e1bf0437738d9bf0761e02fa4c55ff76a87162a0342ce1af899c92-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-13 13:26:36 (3988) [[32mINFO[0m] Trying other mirror.
* 2023-05-13 13:26:42 (3988) [[32mINFO[0m] http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/2d8d438782e1bf0437738d9bf0761e02fa4c55ff76a87162a0342ce1af899c92-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-05-13 13:26:42 (3988) [[32mINFO[0m] Trying other mirror.
* 2023-05-13 13:27:00 (4005) [[32mINFO[0m] 
* 2023-05-13 13:27:00 (1680) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-13 13:27:00 (3974) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-13 13:27:00 (3975) [[32mINFO[0m] 
* 2023-05-13 13:27:00 (3988) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-13 13:27:01 (3988) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-13 13:27:01 (4005) [[32mINFO[0m] 
* 2023-05-13 13:29:13 (1525) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-05-13 13:29:13 (1526) [[31mERROR[0m] https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/bb81f921ee8b3767501f091cc8fe1c36d36543949406f6e3e4ca4a3e27f40e8c-filelists.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/bb81f921ee8b3767501f091cc8fe1c36d36543949406f6e3e4ca4a3e27f40e8c-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirror.natro.com/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.natro.com/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.
http://mirror.radoreservers.com/centos/7.9.2009/updates/x86_64/repodata/bdbc5c7874062ec501476b6ccbdca509572f13238520f9ba4fdab57530be7a92-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.radoreservers.com/centos/7.9.2009/updates/x86_64/repodata/bdbc5c7874062ec501476b6ccbdca509572f13238520f9ba4fdab57530be7a92-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
* 2023-05-13 13:29:13 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-13 13:29:14 (741) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-13 13:29:14 (2136) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ALfRGMfFKX/ea_profile.json
* 2023-05-13 13:29:15 (2159) [[32mINFO[0m] Backed up EA4 profile to /tmp/ALfRGMfFKX/ea_profile.json
* 2023-05-13 13:29:17 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.83.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.90.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-05-13 13:29:18 (251) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-14 02:16:19 (1659) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-14 02:16:19 (3974) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-14 02:16:19 (3975) [[32mINFO[0m] 
* 2023-05-14 02:16:19 (3988) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-14 02:16:19 (3988) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-14 02:16:19 (3988) [[32mINFO[0m]               : epel extras updates
* 2023-05-14 02:16:19 (3988) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-14 02:16:19 (4005) [[32mINFO[0m] 
* 2023-05-14 02:16:19 (3974) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-14 02:16:19 (3975) [[32mINFO[0m] 
* 2023-05-14 02:16:25 (3988) [[32mINFO[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
* 2023-05-14 02:16:25 (3988) [[32mINFO[0m] 14: curl#52 - "Empty reply from server"
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m] 
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m] 
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m] 
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m] 
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m] 
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m] 
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m] 
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]         or
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m] 
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]         compromise:
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m] 
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m] 
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m] Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2023-05-14 02:16:26 (4005) [[32mINFO[0m] 
* 2023-05-14 02:16:26 (1666) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-14 02:16:26 (1680) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-14 02:16:26 (3974) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-14 02:16:26 (3975) [[32mINFO[0m] 
* 2023-05-14 02:16:26 (3988) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-14 02:16:27 (3988) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-14 02:16:27 (4005) [[32mINFO[0m] 
* 2023-05-14 02:19:52 (1525) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-05-14 02:19:52 (1526) [[31mERROR[0m] http://184.94.196.94/cpanelsync/repos/CentOS/7/EA4/repodata/2d8d438782e1bf0437738d9bf0761e02fa4c55ff76a87162a0342ce1af899c92-primary.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.94/cpanelsync/repos/CentOS/7/EA4/repodata/2d8d438782e1bf0437738d9bf0761e02fa4c55ff76a87162a0342ce1af899c92-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/2d8d438782e1bf0437738d9bf0761e02fa4c55ff76a87162a0342ce1af899c92-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/bb81f921ee8b3767501f091cc8fe1c36d36543949406f6e3e4ca4a3e27f40e8c-filelists.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/bb81f921ee8b3767501f091cc8fe1c36d36543949406f6e3e4ca4a3e27f40e8c-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
* 2023-05-14 02:19:52 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-14 02:19:52 (741) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-14 02:19:52 (2136) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/k7qIwhYq7p/ea_profile.json
* 2023-05-14 02:19:54 (2159) [[32mINFO[0m] Backed up EA4 profile to /tmp/k7qIwhYq7p/ea_profile.json
* 2023-05-14 02:19:56 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.83.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.90.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-05-14 02:19:57 (251) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-15 02:20:13 (1659) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-15 02:20:13 (3974) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-15 02:20:13 (3975) [[32mINFO[0m] 
* 2023-05-15 02:20:13 (3988) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-15 02:20:13 (3988) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-15 02:20:13 (3988) [[32mINFO[0m]               : epel extras updates
* 2023-05-15 02:20:14 (3988) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-15 02:20:14 (4005) [[32mINFO[0m] 
* 2023-05-15 02:20:14 (3974) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-15 02:20:14 (3975) [[32mINFO[0m] 
* 2023-05-15 02:20:49 (4005) [[32mINFO[0m] 
* 2023-05-15 02:20:49 (1680) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-15 02:20:49 (3974) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-15 02:20:49 (3975) [[32mINFO[0m] 
* 2023-05-15 02:20:49 (3988) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-15 02:20:52 (3988) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-15 02:20:52 (4005) [[32mINFO[0m] 
* 2023-05-15 02:21:58 (1525) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-05-15 02:21:58 (1526) [[31mERROR[0m] http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/e82b97eebdbc9fc7c84f19092764a4dcb377ebd430a66d6dea77f3fa064cf8e1-filelists.sqlite.bz2: [Errno 12] Timeout on http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/e82b97eebdbc9fc7c84f19092764a4dcb377ebd430a66d6dea77f3fa064cf8e1-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/e82b97eebdbc9fc7c84f19092764a4dcb377ebd430a66d6dea77f3fa064cf8e1-filelists.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-05-15 02:21:58 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-15 02:21:58 (741) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-15 02:21:58 (2136) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/CQyPScZ1Qi/ea_profile.json
* 2023-05-15 02:21:59 (2159) [[32mINFO[0m] Backed up EA4 profile to /tmp/CQyPScZ1Qi/ea_profile.json
* 2023-05-15 02:22:01 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.83.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.90.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-05-15 02:22:02 (251) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-15 13:04:21 (1659) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-15 13:04:21 (3974) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-15 13:04:21 (3975) [[32mINFO[0m] 
* 2023-05-15 13:04:21 (3988) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-15 13:04:21 (3988) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-15 13:04:21 (3988) [[32mINFO[0m]               : epel extras updates
* 2023-05-15 13:04:22 (3988) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-15 13:04:22 (4005) [[32mINFO[0m] 
* 2023-05-15 13:04:22 (3974) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-15 13:04:22 (3975) [[32mINFO[0m] 
* 2023-05-15 13:05:30 (3988) [[32mINFO[0m] http://mirror.netdirekt.com.tr/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.netdirekt.com.tr/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')
* 2023-05-15 13:05:30 (3988) [[32mINFO[0m] Trying other mirror.
* 2023-05-15 13:06:02 (3988) [[32mINFO[0m] http://mirror.netdirekt.com.tr/centos/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.netdirekt.com.tr/centos/7.9.2009/updates/x86_64/repodata/4450409a46c903a5efbdd571f3b1bbbe6705d0629fa50faeccb52875a289ea0c-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-15 13:06:02 (3988) [[32mINFO[0m] Trying other mirror.
* 2023-05-15 13:06:22 (4005) [[32mINFO[0m] 
* 2023-05-15 13:06:22 (1680) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-15 13:06:22 (3974) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-15 13:06:22 (3975) [[32mINFO[0m] 
* 2023-05-15 13:06:22 (3988) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-15 13:06:23 (3988) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-15 13:06:23 (4005) [[32mINFO[0m] 
* 2023-05-15 13:09:56 (1525) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-05-15 13:09:56 (1526) [[31mERROR[0m] http://mirror.natro.com/centos/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on http://mirror.natro.com/centos/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirror.centos.jt.iq/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on http://mirror.centos.jt.iq/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
* 2023-05-15 13:09:56 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-15 13:09:56 (741) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-15 13:09:56 (2136) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/G6Bu5JrzFz/ea_profile.json
* 2023-05-15 13:09:58 (2159) [[32mINFO[0m] Backed up EA4 profile to /tmp/G6Bu5JrzFz/ea_profile.json
* 2023-05-15 13:10:00 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.83.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.90.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-05-15 13:10:01 (251) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-16 02:20:06 (1659) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-16 02:20:06 (3974) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-16 02:20:06 (3975) [[32mINFO[0m] 
* 2023-05-16 02:20:06 (3988) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-16 02:20:06 (3988) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-16 02:20:06 (3988) [[32mINFO[0m]               : epel extras updates
* 2023-05-16 02:20:07 (3988) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-16 02:20:07 (4005) [[32mINFO[0m] 
* 2023-05-16 02:20:07 (3974) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-16 02:20:07 (3975) [[32mINFO[0m] 
* 2023-05-16 02:21:23 (4005) [[32mINFO[0m] 
* 2023-05-16 02:21:23 (1680) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-16 02:21:23 (3974) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-16 02:21:23 (3975) [[32mINFO[0m] 
* 2023-05-16 02:21:24 (3988) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-16 02:21:27 (3988) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-16 02:21:27 (4005) [[32mINFO[0m] 
* 2023-05-16 02:24:39 (1525) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-05-16 02:24:39 (1526) [[31mERROR[0m] http://mirror.netdirekt.com.tr/centos/7.9.2009/updates/x86_64/repodata/553ee4a1428f4d8208841ff88ed15a72dca0e16b251762875a08233c304b3dba-filelists.sqlite.bz2: [Errno 12] Timeout on http://mirror.netdirekt.com.tr/centos/7.9.2009/updates/x86_64/repodata/553ee4a1428f4d8208841ff88ed15a72dca0e16b251762875a08233c304b3dba-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
* 2023-05-16 02:24:39 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-16 02:24:43 (741) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-16 02:24:44 (2136) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/t_x9Nzq7KE/ea_profile.json
* 2023-05-16 02:24:46 (2159) [[32mINFO[0m] Backed up EA4 profile to /tmp/t_x9Nzq7KE/ea_profile.json
* 2023-05-16 02:24:48 (148) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.83.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.90.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-05-16 02:24:49 (251) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-19 02:39:10 (1699) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-19 02:39:10 (4085) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-19 02:39:10 (4086) [[32mINFO[0m] 
* 2023-05-19 02:39:11 (4099) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-19 02:39:11 (4099) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-19 02:39:11 (4099) [[32mINFO[0m]               : epel extras updates
* 2023-05-19 02:39:11 (4099) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-19 02:39:11 (4116) [[32mINFO[0m] 
* 2023-05-19 02:39:11 (4085) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-19 02:39:11 (4086) [[32mINFO[0m] 
* 2023-05-19 02:39:49 (4116) [[32mINFO[0m] 
* 2023-05-19 02:39:49 (1720) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-19 02:39:49 (4085) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-19 02:39:49 (4086) [[32mINFO[0m] 
* 2023-05-19 02:39:49 (4099) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-19 02:39:50 (4099) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-19 02:39:50 (4116) [[32mINFO[0m] 
* 2023-05-19 02:40:47 (777) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-19 02:40:47 (2235) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/l2h2J660qn/ea_profile.json
* 2023-05-19 02:40:49 (2258) [[32mINFO[0m] Backed up EA4 profile to /tmp/l2h2J660qn/ea_profile.json
* 2023-05-19 02:40:51 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.83.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.90.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-05-19 02:40:52 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-19 16:06:00 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-05-19 16:06:01 (1699) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-19 16:06:01 (4085) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-19 16:06:01 (4086) [[32mINFO[0m] 
* 2023-05-19 16:06:01 (4099) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-19 16:06:02 (4099) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103 base
* 2023-05-19 16:06:02 (4099) [[32mINFO[0m]               : epel extras updates
* 2023-05-19 16:06:02 (4099) [[32mINFO[0m] Other repos take up 404 k of disk space (use --verbose for details)
* 2023-05-19 16:06:02 (4116) [[32mINFO[0m] 
* 2023-05-19 16:06:02 (4085) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-19 16:06:02 (4086) [[32mINFO[0m] 
* 2023-05-19 16:06:56 (4116) [[32mINFO[0m] 
* 2023-05-19 16:06:56 (1720) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-19 16:06:56 (4085) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-19 16:06:56 (4086) [[32mINFO[0m] 
* 2023-05-19 16:06:57 (4099) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-19 16:06:59 (4099) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-19 16:06:59 (4116) [[32mINFO[0m] 
* 2023-05-19 16:09:39 (1565) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-05-19 16:09:39 (1566) [[31mERROR[0m] http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/80761e3cb83af9a45fa0e7e5bf26f3c31c7a653c8fdf570afcdb66b6d74c8707-other.sqlite.bz2: [Errno 12] Timeout on http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/80761e3cb83af9a45fa0e7e5bf26f3c31c7a653c8fdf570afcdb66b6d74c8707-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://110.232.143.226/cpanelsync/repos/CentOS/7/EA4/repodata/80761e3cb83af9a45fa0e7e5bf26f3c31c7a653c8fdf570afcdb66b6d74c8707-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/bb81f921ee8b3767501f091cc8fe1c36d36543949406f6e3e4ca4a3e27f40e8c-filelists.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/bb81f921ee8b3767501f091cc8fe1c36d36543949406f6e3e4ca4a3e27f40e8c-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/bb81f921ee8b3767501f091cc8fe1c36d36543949406f6e3e4ca4a3e27f40e8c-filelists.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.3/yum/centos/7/x86_64/repodata/bb81f921ee8b3767501f091cc8fe1c36d36543949406f6e3e4ca4a3e27f40e8c-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
* 2023-05-19 16:09:39 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-19 16:09:47 (777) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-19 16:09:47 (2235) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ceua45MJNW/ea_profile.json
* 2023-05-19 16:09:50 (2258) [[32mINFO[0m] Backed up EA4 profile to /tmp/ceua45MJNW/ea_profile.json
* 2023-05-19 16:09:52 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.83.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.90.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-05-19 16:09:53 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-21 02:28:35 (1699) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-21 02:28:35 (4085) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-21 02:28:35 (4086) [[32mINFO[0m] 
* 2023-05-21 02:28:36 (4099) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-21 02:28:36 (4099) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-05-21 02:28:36 (4099) [[32mINFO[0m]               : epel extras updates
* 2023-05-21 02:28:36 (4099) [[32mINFO[0m] Other repos take up 4.5 M of disk space (use --verbose for details)
* 2023-05-21 02:28:36 (4116) [[32mINFO[0m] 
* 2023-05-21 02:28:36 (4085) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-21 02:28:36 (4086) [[32mINFO[0m] 
* 2023-05-21 02:29:39 (4116) [[32mINFO[0m] 
* 2023-05-21 02:29:39 (1706) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-21 02:29:39 (1720) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-21 02:29:39 (4085) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-21 02:29:39 (4086) [[32mINFO[0m] 
* 2023-05-21 02:29:40 (4099) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-21 02:29:49 (4099) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-21 02:29:49 (4116) [[32mINFO[0m] 
* 2023-05-21 02:30:34 (777) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-21 02:30:34 (2235) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DkNHZGIC5c/ea_profile.json
* 2023-05-21 02:30:36 (2258) [[32mINFO[0m] Backed up EA4 profile to /tmp/DkNHZGIC5c/ea_profile.json
* 2023-05-21 02:30:39 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.83.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.90.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-05-21 02:30:40 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-21 10:54:28 (1699) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-21 10:54:28 (4085) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-21 10:54:28 (4086) [[32mINFO[0m] 
* 2023-05-21 10:54:29 (4099) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-21 10:54:29 (4099) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-05-21 10:54:29 (4099) [[32mINFO[0m]               : epel extras updates
* 2023-05-21 10:54:29 (4099) [[32mINFO[0m] Other repos take up 4.5 M of disk space (use --verbose for details)
* 2023-05-21 10:54:29 (4116) [[32mINFO[0m] 
* 2023-05-21 10:54:29 (4085) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-21 10:54:29 (4086) [[32mINFO[0m] 
* 2023-05-21 10:55:25 (4099) [[32mINFO[0m] http://repo.ugm.ac.id/epel/7/x86_64/repodata/06180a7f42f57edbc7a45d254af7930a5d7ac0b817ecafbc831fd6520aa3db66-updateinfo.xml.bz2: [Errno 12] Timeout on http://repo.ugm.ac.id/epel/7/x86_64/repodata/06180a7f42f57edbc7a45d254af7930a5d7ac0b817ecafbc831fd6520aa3db66-updateinfo.xml.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-21 10:55:25 (4099) [[32mINFO[0m] Trying other mirror.
* 2023-05-21 10:55:47 (4099) [[32mINFO[0m] https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/df03da6b38445eb3dfb427a7348640a6becae7a2917f87a6ecf5b77c41b2b445-primary.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/df03da6b38445eb3dfb427a7348640a6becae7a2917f87a6ecf5b77c41b2b445-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-21 10:55:47 (4099) [[32mINFO[0m] Trying other mirror.
* 2023-05-21 10:56:11 (4099) [[32mINFO[0m] http://mirror.netdirekt.com.tr/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.netdirekt.com.tr/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')
* 2023-05-21 10:56:11 (4099) [[32mINFO[0m] Trying other mirror.
* 2023-05-21 10:56:48 (4099) [[32mINFO[0m] https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/df03da6b38445eb3dfb427a7348640a6becae7a2917f87a6ecf5b77c41b2b445-primary.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/df03da6b38445eb3dfb427a7348640a6becae7a2917f87a6ecf5b77c41b2b445-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-21 10:56:48 (4099) [[32mINFO[0m] Trying other mirror.
* 2023-05-21 10:57:19 (4099) [[32mINFO[0m] https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/df03da6b38445eb3dfb427a7348640a6becae7a2917f87a6ecf5b77c41b2b445-primary.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/df03da6b38445eb3dfb427a7348640a6becae7a2917f87a6ecf5b77c41b2b445-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-21 10:57:19 (4099) [[32mINFO[0m] Trying other mirror.
* 2023-05-21 10:58:11 (4116) [[32mINFO[0m] 
* 2023-05-21 10:58:11 (1720) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-21 10:58:11 (4085) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-21 10:58:11 (4086) [[32mINFO[0m] 
* 2023-05-21 10:58:11 (4099) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-21 10:58:12 (4099) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-21 10:58:12 (4116) [[32mINFO[0m] 
* 2023-05-21 11:02:20 (1565) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-05-21 11:02:20 (1566) [[31mERROR[0m] https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/3d986812cfaba91f42e94e65562b9d7d9241d9e7c041246d6d2ca0d253323ccb-filelists.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/3d986812cfaba91f42e94e65562b9d7d9241d9e7c041246d6d2ca0d253323ccb-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/642827eb0e9be6cf35e984304fd3393533761b299c603a0d23d0347900e13a02-prestodelta.xml.gz: [Errno 12] Timeout on http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/642827eb0e9be6cf35e984304fd3393533761b299c603a0d23d0347900e13a02-prestodelta.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
http://mirror.natro.com/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.natro.com/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.
https://epel.excellmedia.net/7/x86_64/repodata/642827eb0e9be6cf35e984304fd3393533761b299c603a0d23d0347900e13a02-prestodelta.xml.gz: [Errno 12] Timeout on https://epel.excellmedia.net/7/x86_64/repodata/642827eb0e9be6cf35e984304fd3393533761b299c603a0d23d0347900e13a02-prestodelta.xml.gz: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
Trying other mirror.
https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/642827eb0e9be6cf35e984304fd3393533761b299c603a0d23d0347900e13a02-prestodelta.xml.gz: [Errno 12] Timeout on https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/642827eb0e9be6cf35e984304fd3393533761b299c603a0d23d0347900e13a02-prestodelta.xml.gz: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')
Trying other mirror.
http://mirror.netdirekt.com.tr/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.netdirekt.com.tr/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.
http://mirror.radoreservers.com/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.radoreservers.com/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-05-21 11:02:20 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-21 11:02:20 (777) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-21 11:02:20 (2235) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9zn9TnBk4F/ea_profile.json
* 2023-05-21 11:02:22 (2258) [[32mINFO[0m] Backed up EA4 profile to /tmp/9zn9TnBk4F/ea_profile.json
* 2023-05-21 11:02:25 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-21 11:25:12 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-05-21 11:25:13 (1699) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-21 11:25:13 (4085) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-21 11:25:13 (4086) [[32mINFO[0m] 
* 2023-05-21 11:25:13 (4099) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-21 11:25:13 (4099) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-05-21 11:25:13 (4099) [[32mINFO[0m]               : epel extras updates
* 2023-05-21 11:25:13 (4099) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-05-21 11:25:13 (4116) [[32mINFO[0m] 
* 2023-05-21 11:25:13 (4085) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-21 11:25:13 (4086) [[32mINFO[0m] 
* 2023-05-21 11:26:46 (4099) [[32mINFO[0m] https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/df03da6b38445eb3dfb427a7348640a6becae7a2917f87a6ecf5b77c41b2b445-primary.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/df03da6b38445eb3dfb427a7348640a6becae7a2917f87a6ecf5b77c41b2b445-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-21 11:26:46 (4099) [[32mINFO[0m] Trying other mirror.
* 2023-05-21 11:27:06 (4116) [[32mINFO[0m] 
* 2023-05-21 11:27:06 (1720) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-21 11:27:06 (4085) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-21 11:27:06 (4086) [[32mINFO[0m] 
* 2023-05-21 11:27:07 (4099) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-21 11:27:08 (4099) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-21 11:27:08 (4116) [[32mINFO[0m] 
* 2023-05-21 11:32:03 (1565) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-05-21 11:32:03 (1566) [[31mERROR[0m] https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/3d986812cfaba91f42e94e65562b9d7d9241d9e7c041246d6d2ca0d253323ccb-filelists.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/3d986812cfaba91f42e94e65562b9d7d9241d9e7c041246d6d2ca0d253323ccb-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/3d986812cfaba91f42e94e65562b9d7d9241d9e7c041246d6d2ca0d253323ccb-filelists.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/3d986812cfaba91f42e94e65562b9d7d9241d9e7c041246d6d2ca0d253323ccb-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/3d986812cfaba91f42e94e65562b9d7d9241d9e7c041246d6d2ca0d253323ccb-filelists.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/3d986812cfaba91f42e94e65562b9d7d9241d9e7c041246d6d2ca0d253323ccb-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
* 2023-05-21 11:32:03 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-21 11:32:03 (777) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-21 11:32:05 (2235) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ewCVEjGKNk/ea_profile.json
* 2023-05-21 11:32:07 (2258) [[32mINFO[0m] Backed up EA4 profile to /tmp/ewCVEjGKNk/ea_profile.json
* 2023-05-21 11:32:10 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-22 02:15:12 (1699) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-22 02:15:12 (4085) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-22 02:15:12 (4086) [[32mINFO[0m] 
* 2023-05-22 02:15:12 (4099) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-22 02:15:12 (4099) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-05-22 02:15:12 (4099) [[32mINFO[0m]               : epel extras updates
* 2023-05-22 02:15:12 (4099) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-05-22 02:15:12 (4116) [[32mINFO[0m] 
* 2023-05-22 02:15:12 (4085) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-22 02:15:12 (4086) [[32mINFO[0m] 
* 2023-05-22 02:16:26 (4099) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/84d4a7453744486389333e6dc8871222dd6dc38e397588093178570499dec880-comps-Everything.x86_64.xml.gz: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/84d4a7453744486389333e6dc8871222dd6dc38e397588093178570499dec880-comps-Everything.x86_64.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-22 02:16:26 (4099) [[32mINFO[0m] Trying other mirror.
* 2023-05-22 02:17:02 (4099) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/598709265aa176f7ac1c081d83f941fcdbe8496f5624e3ce5cbfb6ae659ff969-primary.sqlite.bz2: [Errno 12] Timeout on http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/598709265aa176f7ac1c081d83f941fcdbe8496f5624e3ce5cbfb6ae659ff969-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-22 02:17:02 (4099) [[32mINFO[0m] Trying other mirror.
* 2023-05-22 02:17:04 (4099) [[32mINFO[0m] http://mirror.radoreservers.com/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.radoreservers.com/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')
* 2023-05-22 02:17:04 (4099) [[32mINFO[0m] Trying other mirror.
* 2023-05-22 02:17:35 (4099) [[32mINFO[0m] http://mirror.verinomi.com/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.verinomi.com/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds')
* 2023-05-22 02:17:35 (4099) [[32mINFO[0m] Trying other mirror.
* 2023-05-22 02:18:23 (4099) [[32mINFO[0m] http://mirror.netdirekt.com.tr/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.netdirekt.com.tr/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')
* 2023-05-22 02:18:23 (4099) [[32mINFO[0m] Trying other mirror.
* 2023-05-22 02:19:00 (4099) [[32mINFO[0m] http://mirror.saglayici.com/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.saglayici.com/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')
* 2023-05-22 02:19:00 (4099) [[32mINFO[0m] Trying other mirror.
* 2023-05-22 02:19:15 (4116) [[32mINFO[0m] 
* 2023-05-22 02:19:15 (1720) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-22 02:19:15 (4085) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-22 02:19:15 (4086) [[32mINFO[0m] 
* 2023-05-22 02:19:16 (4099) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-22 02:19:17 (4099) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-22 02:19:17 (4116) [[32mINFO[0m] 
* 2023-05-22 02:19:56 (1565) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-05-22 02:19:56 (1566) [[31mERROR[0m] http://184.94.196.93/cpanelsync/repos/CentOS/7/EA4/repodata/80761e3cb83af9a45fa0e7e5bf26f3c31c7a653c8fdf570afcdb66b6d74c8707-other.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
Trying other mirror.
* 2023-05-22 02:19:56 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-22 02:19:57 (777) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-22 02:19:57 (2235) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7inajre9ut/ea_profile.json
* 2023-05-22 02:19:58 (2258) [[32mINFO[0m] Backed up EA4 profile to /tmp/7inajre9ut/ea_profile.json
* 2023-05-22 02:20:01 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-23 02:17:55 (1699) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-23 02:17:55 (4085) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-23 02:17:55 (4086) [[32mINFO[0m] 
* 2023-05-23 02:17:55 (4099) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-23 02:17:55 (4099) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-05-23 02:17:55 (4099) [[32mINFO[0m]               : epel extras updates
* 2023-05-23 02:17:55 (4099) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-05-23 02:17:55 (4116) [[32mINFO[0m] 
* 2023-05-23 02:17:55 (4085) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-23 02:17:55 (4086) [[32mINFO[0m] 
* 2023-05-23 02:18:31 (4116) [[32mINFO[0m] 
* 2023-05-23 02:18:31 (1720) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-23 02:18:31 (4085) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-23 02:18:31 (4086) [[32mINFO[0m] 
* 2023-05-23 02:18:31 (4099) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-23 02:18:32 (4099) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-23 02:18:32 (4116) [[32mINFO[0m] 
* 2023-05-23 02:19:20 (777) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-23 02:19:21 (2235) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ECveZRbdqM/ea_profile.json
* 2023-05-23 02:19:23 (2258) [[32mINFO[0m] Backed up EA4 profile to /tmp/ECveZRbdqM/ea_profile.json
* 2023-05-23 02:19:26 (268) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-05-24 02:14:39 (1699) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-24 02:14:39 (4085) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-24 02:14:39 (4086) [[32mINFO[0m] 
* 2023-05-24 02:14:39 (4099) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-24 02:14:39 (4099) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-05-24 02:14:39 (4099) [[32mINFO[0m]               : epel extras updates
* 2023-05-24 02:14:40 (4099) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-05-24 02:14:40 (4116) [[32mINFO[0m] 
* 2023-05-24 02:14:40 (4085) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-24 02:14:40 (4086) [[32mINFO[0m] 
* 2023-05-24 02:16:09 (4116) [[32mINFO[0m] 
* 2023-05-24 02:16:09 (1720) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-24 02:16:09 (4085) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-24 02:16:09 (4086) [[32mINFO[0m] 
* 2023-05-24 02:16:09 (4099) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-24 02:16:10 (4099) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-24 02:16:10 (4116) [[32mINFO[0m] 
* 2023-05-24 02:16:43 (777) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-24 02:16:43 (2235) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oeo89ALLGG/ea_profile.json
* 2023-05-24 02:16:45 (2258) [[32mINFO[0m] Backed up EA4 profile to /tmp/oeo89ALLGG/ea_profile.json
* 2023-05-24 02:16:48 (268) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-05-25 02:19:43 (1699) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-25 02:19:43 (4085) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-25 02:19:43 (4086) [[32mINFO[0m] 
* 2023-05-25 02:19:43 (4099) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-25 02:19:44 (4099) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-05-25 02:19:44 (4099) [[32mINFO[0m]               : epel extras updates
* 2023-05-25 02:19:44 (4099) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-05-25 02:19:44 (4116) [[32mINFO[0m] 
* 2023-05-25 02:19:44 (4085) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-25 02:19:44 (4086) [[32mINFO[0m] 
* 2023-05-25 02:20:39 (4116) [[32mINFO[0m] 
* 2023-05-25 02:20:39 (1720) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-25 02:20:39 (4085) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-25 02:20:39 (4086) [[32mINFO[0m] 
* 2023-05-25 02:20:39 (4099) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-25 02:20:40 (4099) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-25 02:20:40 (4116) [[32mINFO[0m] 
* 2023-05-25 02:21:44 (777) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-25 02:21:45 (2235) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Nm_1Ck0WAx/ea_profile.json
* 2023-05-25 02:21:46 (2258) [[32mINFO[0m] Backed up EA4 profile to /tmp/Nm_1Ck0WAx/ea_profile.json
* 2023-05-25 02:21:49 (268) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-05-26 16:02:00 (1699) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-26 16:02:00 (4085) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-26 16:02:00 (4086) [[32mINFO[0m] 
* 2023-05-26 16:02:00 (4099) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-26 16:02:00 (4099) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-05-26 16:02:00 (4099) [[32mINFO[0m]               : epel extras updates
* 2023-05-26 16:02:01 (4099) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-05-26 16:02:01 (4116) [[32mINFO[0m] 
* 2023-05-26 16:02:01 (4085) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-26 16:02:01 (4086) [[32mINFO[0m] 
* 2023-05-26 16:10:08 (4099) [[32mINFO[0m] http://ftp.linux.org.tr/centos/7.9.2009/updates/x86_64/repodata/941245c0415b6ba986b382d658592904d5f013672cbf0131287f811810b9fb0b-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-05-26 16:10:08 (4099) [[32mINFO[0m] Trying other mirror.
* 2023-05-26 16:19:37 (4116) [[32mINFO[0m] 
* 2023-05-26 16:19:37 (1720) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-26 16:19:37 (4085) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-26 16:19:37 (4086) [[32mINFO[0m] 
* 2023-05-26 16:19:37 (4099) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-26 16:19:39 (4099) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-26 16:19:39 (4116) [[32mINFO[0m] 
* 2023-05-26 16:22:19 (1565) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-05-26 16:22:19 (1566) [[31mERROR[0m] http://mirror.radoreservers.com/centos/7.9.2009/extras/x86_64/repodata/78c0e5530bc46d128e18eca9ff16b2d0651efdb33434408f8ff1db4d14f1bb99-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.radoreservers.com/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-05-26 16:22:19 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-26 16:22:19 (777) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-26 16:22:19 (2235) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uMNh4ZoQRM/ea_profile.json
* 2023-05-26 16:22:21 (2258) [[32mINFO[0m] Backed up EA4 profile to /tmp/uMNh4ZoQRM/ea_profile.json
* 2023-05-26 16:22:24 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-27 02:15:56 (1699) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-27 02:15:56 (4085) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-27 02:15:56 (4086) [[32mINFO[0m] 
* 2023-05-27 02:15:56 (4099) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-27 02:15:56 (4099) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-05-27 02:15:56 (4099) [[32mINFO[0m]               : epel extras updates
* 2023-05-27 02:15:56 (4099) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-05-27 02:15:56 (4116) [[32mINFO[0m] 
* 2023-05-27 02:15:56 (4085) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-27 02:15:56 (4086) [[32mINFO[0m] 
* 2023-05-27 02:21:38 (4116) [[32mINFO[0m] 
* 2023-05-27 02:21:38 (1720) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-27 02:21:38 (4085) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-27 02:21:38 (4086) [[32mINFO[0m] 
* 2023-05-27 02:21:38 (4099) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-27 02:21:40 (4099) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-27 02:21:40 (4116) [[32mINFO[0m] 
* 2023-05-27 02:22:20 (777) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-27 02:22:20 (2235) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4u_4YFRYsO/ea_profile.json
* 2023-05-27 02:22:21 (2258) [[32mINFO[0m] Backed up EA4 profile to /tmp/4u_4YFRYsO/ea_profile.json
* 2023-05-27 02:22:24 (268) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-05-28 02:17:20 (1699) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-28 02:17:20 (4085) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-28 02:17:20 (4086) [[32mINFO[0m] 
* 2023-05-28 02:17:20 (4099) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-28 02:17:20 (4099) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-05-28 02:17:20 (4099) [[32mINFO[0m]               : epel extras updates
* 2023-05-28 02:17:20 (4099) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-05-28 02:17:20 (4116) [[32mINFO[0m] 
* 2023-05-28 02:17:20 (4085) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-28 02:17:20 (4086) [[32mINFO[0m] 
* 2023-05-28 02:17:59 (4116) [[32mINFO[0m] 
* 2023-05-28 02:17:59 (1720) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-28 02:17:59 (4085) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-28 02:17:59 (4086) [[32mINFO[0m] 
* 2023-05-28 02:17:59 (4099) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-28 02:18:00 (4099) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-28 02:18:00 (4116) [[32mINFO[0m] 
* 2023-05-28 02:20:44 (1565) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-05-28 02:20:44 (1566) [[31mERROR[0m] http://mirror.radoreservers.com/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.radoreservers.com/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-05-28 02:20:44 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-28 02:20:45 (777) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-28 02:20:45 (2235) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UgJ9LuWsvn/ea_profile.json
* 2023-05-28 02:20:46 (2258) [[32mINFO[0m] Backed up EA4 profile to /tmp/UgJ9LuWsvn/ea_profile.json
* 2023-05-28 02:20:49 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
* 2023-05-29 02:15:54 (1699) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-29 02:15:54 (4085) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-29 02:15:54 (4086) [[32mINFO[0m] 
* 2023-05-29 02:15:55 (4099) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-29 02:15:55 (4099) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-05-29 02:15:55 (4099) [[32mINFO[0m]               : epel extras updates
* 2023-05-29 02:15:55 (4099) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-05-29 02:15:55 (4116) [[32mINFO[0m] 
* 2023-05-29 02:15:55 (4085) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-29 02:15:55 (4086) [[32mINFO[0m] 
* 2023-05-29 02:17:48 (4099) [[32mINFO[0m] http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/734f657df436c7e9955fc2676b51f53804e80dbbbc11b38e590ac8fafda76c01-primary.sqlite.bz2: [Errno 12] Timeout on http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/734f657df436c7e9955fc2676b51f53804e80dbbbc11b38e590ac8fafda76c01-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-05-29 02:17:48 (4099) [[32mINFO[0m] Trying other mirror.
* 2023-05-29 02:17:49 (4099) [[32mINFO[0m] http://185.157.208.252/cpanelsync/repos/CentOS/7/EA4/repodata/734f657df436c7e9955fc2676b51f53804e80dbbbc11b38e590ac8fafda76c01-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-05-29 02:17:49 (4099) [[32mINFO[0m] Trying other mirror.
* 2023-05-29 02:18:07 (4116) [[32mINFO[0m] 
* 2023-05-29 02:18:07 (1720) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-29 02:18:07 (4085) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-29 02:18:07 (4086) [[32mINFO[0m] 
* 2023-05-29 02:18:07 (4099) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-29 02:18:08 (4099) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-29 02:18:08 (4116) [[32mINFO[0m] 
* 2023-05-29 02:18:34 (777) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-29 02:18:34 (2235) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_k_ZN23ViP/ea_profile.json
* 2023-05-29 02:18:35 (2258) [[32mINFO[0m] Backed up EA4 profile to /tmp/_k_ZN23ViP/ea_profile.json
* 2023-05-29 02:18:38 (268) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-05-30 02:17:27 (1699) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-30 02:17:27 (4085) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-30 02:17:27 (4086) [[32mINFO[0m] 
* 2023-05-30 02:17:28 (4099) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-30 02:17:28 (4099) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-05-30 02:17:28 (4099) [[32mINFO[0m]               : epel extras updates
* 2023-05-30 02:17:28 (4099) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-05-30 02:17:28 (4116) [[32mINFO[0m] 
* 2023-05-30 02:17:28 (4085) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-30 02:17:28 (4086) [[32mINFO[0m] 
* 2023-05-30 02:18:50 (4116) [[32mINFO[0m] 
* 2023-05-30 02:18:50 (1720) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-30 02:18:50 (4085) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-30 02:18:50 (4086) [[32mINFO[0m] 
* 2023-05-30 02:18:50 (4099) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-30 02:18:51 (4099) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-30 02:18:51 (4116) [[32mINFO[0m] 
* 2023-05-30 02:19:36 (777) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-30 02:19:36 (2235) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BHyYObY9t6/ea_profile.json
* 2023-05-30 02:19:38 (2258) [[32mINFO[0m] Backed up EA4 profile to /tmp/BHyYObY9t6/ea_profile.json
* 2023-05-30 02:19:41 (268) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-05-31 02:29:09 (1699) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-05-31 02:29:09 (4085) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-05-31 02:29:09 (4086) [[32mINFO[0m] 
* 2023-05-31 02:29:09 (4099) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-31 02:29:09 (4099) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-05-31 02:29:09 (4099) [[32mINFO[0m]               : epel extras updates
* 2023-05-31 02:29:09 (4099) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-05-31 02:29:09 (4116) [[32mINFO[0m] 
* 2023-05-31 02:29:09 (4085) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-05-31 02:29:09 (4086) [[32mINFO[0m] 
* 2023-05-31 02:30:20 (4116) [[32mINFO[0m] 
* 2023-05-31 02:30:20 (1720) [[32mINFO[0m] Checking /scripts/sysup
* 2023-05-31 02:30:20 (4085) [[32mINFO[0m] Running: /scripts/sysup
* 2023-05-31 02:30:20 (4086) [[32mINFO[0m] 
* 2023-05-31 02:30:20 (4099) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-31 02:30:21 (4099) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-05-31 02:30:21 (4116) [[32mINFO[0m] 
* 2023-05-31 02:31:08 (777) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-31 02:31:08 (2235) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Gjc8h9cb0U/ea_profile.json
* 2023-05-31 02:31:09 (2258) [[32mINFO[0m] Backed up EA4 profile to /tmp/Gjc8h9cb0U/ea_profile.json
* 2023-05-31 02:31:12 (268) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-01 02:19:20 (1699) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-01 02:19:20 (4085) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-01 02:19:20 (4086) [[32mINFO[0m] 
* 2023-06-01 02:19:20 (4099) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-01 02:19:20 (4099) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-01 02:19:20 (4099) [[32mINFO[0m]               : epel extras updates
* 2023-06-01 02:19:20 (4099) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-01 02:19:20 (4116) [[32mINFO[0m] 
* 2023-06-01 02:19:20 (4085) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-01 02:19:20 (4086) [[32mINFO[0m] 
* 2023-06-01 02:21:53 (4116) [[32mINFO[0m] 
* 2023-06-01 02:21:53 (1720) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-01 02:21:53 (4085) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-01 02:21:53 (4086) [[32mINFO[0m] 
* 2023-06-01 02:21:53 (4099) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-01 02:21:55 (4099) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-01 02:21:55 (4116) [[32mINFO[0m] 
* 2023-06-01 02:23:09 (777) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-01 02:23:09 (2235) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FYOYuCtDEz/ea_profile.json
* 2023-06-01 02:23:11 (2258) [[32mINFO[0m] Backed up EA4 profile to /tmp/FYOYuCtDEz/ea_profile.json
* 2023-06-01 02:23:14 (268) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-02 02:19:45 (1699) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-02 02:19:45 (4085) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-02 02:19:45 (4086) [[32mINFO[0m] 
* 2023-06-02 02:19:45 (4099) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-02 02:19:45 (4099) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-02 02:19:45 (4099) [[32mINFO[0m]               : epel extras updates
* 2023-06-02 02:19:46 (4099) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-02 02:19:46 (4116) [[32mINFO[0m] 
* 2023-06-02 02:19:46 (4085) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-02 02:19:46 (4086) [[32mINFO[0m] 
* 2023-06-02 02:21:03 (4116) [[32mINFO[0m] 
* 2023-06-02 02:21:03 (1720) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-02 02:21:03 (4085) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-02 02:21:03 (4086) [[32mINFO[0m] 
* 2023-06-02 02:21:03 (4099) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-02 02:21:04 (4099) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-02 02:21:04 (4116) [[32mINFO[0m] 
* 2023-06-02 02:22:19 (777) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-02 02:22:19 (2235) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wzgYrvNcxK/ea_profile.json
* 2023-06-02 02:22:20 (2258) [[32mINFO[0m] Backed up EA4 profile to /tmp/wzgYrvNcxK/ea_profile.json
* 2023-06-02 02:22:23 (268) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-02 15:59:26 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-02 15:59:26 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-02 15:59:26 (4089) [[32mINFO[0m] 
* 2023-06-02 15:59:26 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-02 15:59:26 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-02 15:59:26 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-02 15:59:26 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-02 15:59:26 (4119) [[32mINFO[0m] 
* 2023-06-02 15:59:26 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-02 15:59:26 (4089) [[32mINFO[0m] 
* 2023-06-02 16:01:08 (4119) [[32mINFO[0m] 
* 2023-06-02 16:01:08 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-02 16:01:08 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-02 16:01:08 (4089) [[32mINFO[0m] 
* 2023-06-02 16:01:09 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-02 16:01:10 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-02 16:01:10 (4119) [[32mINFO[0m] 
* 2023-06-02 16:04:32 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-02 16:04:32 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/kly1COWpQq/ea_profile.json
* 2023-06-02 16:04:33 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/kly1COWpQq/ea_profile.json
* 2023-06-02 16:04:36 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-03 02:17:59 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-03 02:17:59 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-03 02:17:59 (4089) [[32mINFO[0m] 
* 2023-06-03 02:18:00 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-03 02:18:00 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-03 02:18:00 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-03 02:18:00 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-03 02:18:00 (4119) [[32mINFO[0m] 
* 2023-06-03 02:18:00 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-03 02:18:00 (4089) [[32mINFO[0m] 
* 2023-06-03 02:19:14 (4119) [[32mINFO[0m] 
* 2023-06-03 02:19:14 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-03 02:19:14 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-03 02:19:14 (4089) [[32mINFO[0m] 
* 2023-06-03 02:19:14 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-03 02:19:16 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-03 02:19:16 (4119) [[32mINFO[0m] 
* 2023-06-03 02:20:05 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-03 02:20:05 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VSJDKNoipk/ea_profile.json
* 2023-06-03 02:20:06 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/VSJDKNoipk/ea_profile.json
* 2023-06-03 02:20:09 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-04 02:22:56 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-04 02:22:56 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-04 02:22:56 (4089) [[32mINFO[0m] 
* 2023-06-04 02:22:56 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-04 02:22:56 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-04 02:22:56 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-04 02:22:57 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-04 02:22:57 (4119) [[32mINFO[0m] 
* 2023-06-04 02:22:57 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-04 02:22:57 (4089) [[32mINFO[0m] 
* 2023-06-04 02:29:45 (4119) [[32mINFO[0m] 
* 2023-06-04 02:29:45 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-04 02:29:45 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-04 02:29:45 (4089) [[32mINFO[0m] 
* 2023-06-04 02:29:45 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-04 02:29:46 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-04 02:29:46 (4119) [[32mINFO[0m] 
* 2023-06-04 02:33:53 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-04 02:33:53 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nO6NeXfcyo/ea_profile.json
* 2023-06-04 02:33:55 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/nO6NeXfcyo/ea_profile.json
* 2023-06-04 02:33:58 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-05 02:21:43 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-05 02:21:43 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-05 02:21:43 (4089) [[32mINFO[0m] 
* 2023-06-05 02:21:44 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-05 02:21:44 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-05 02:21:44 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-05 02:21:44 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-05 02:21:44 (4119) [[32mINFO[0m] 
* 2023-06-05 02:21:44 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-05 02:21:44 (4089) [[32mINFO[0m] 
* 2023-06-05 02:22:58 (4119) [[32mINFO[0m] 
* 2023-06-05 02:22:58 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-05 02:22:58 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-05 02:22:58 (4089) [[32mINFO[0m] 
* 2023-06-05 02:22:59 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-05 02:23:00 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-05 02:23:00 (4119) [[32mINFO[0m] 
* 2023-06-05 02:25:29 (1566) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-06-05 02:25:29 (1567) [[31mERROR[0m] http://repo.boun.edu.tr/centos/7.9.2009/extras/x86_64/repodata/78c0e5530bc46d128e18eca9ff16b2d0651efdb33434408f8ff1db4d14f1bb99-other.sqlite.bz2: [Errno 12] Timeout on http://repo.boun.edu.tr/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-05 02:25:29 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-05 02:25:30 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-05 02:25:30 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IYoe_5_9S5/ea_profile.json
* 2023-06-05 02:25:31 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/IYoe_5_9S5/ea_profile.json
* 2023-06-05 02:25:34 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-06 02:16:46 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-06-06 02:16:47 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-06 02:16:47 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-06 02:16:47 (4089) [[32mINFO[0m] 
* 2023-06-06 02:16:47 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-06 02:16:48 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-06 02:16:48 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-06 02:16:48 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-06 02:16:48 (4119) [[32mINFO[0m] 
* 2023-06-06 02:16:48 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-06 02:16:48 (4089) [[32mINFO[0m] 
* 2023-06-06 02:18:00 (4119) [[32mINFO[0m] 
* 2023-06-06 02:18:00 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-06 02:18:00 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-06 02:18:00 (4089) [[32mINFO[0m] 
* 2023-06-06 02:18:00 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-06 02:18:01 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-06 02:18:01 (4119) [[32mINFO[0m] 
* 2023-06-06 02:18:53 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-06 02:18:53 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/02xUuDSpz5/ea_profile.json
* 2023-06-06 02:18:54 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/02xUuDSpz5/ea_profile.json
* 2023-06-06 02:18:58 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-07 02:17:12 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-06-07 02:17:13 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-07 02:17:13 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-07 02:17:13 (4089) [[32mINFO[0m] 
* 2023-06-07 02:17:14 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-07 02:17:14 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-07 02:17:14 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-07 02:17:14 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-07 02:17:14 (4119) [[32mINFO[0m] 
* 2023-06-07 02:17:14 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-07 02:17:14 (4089) [[32mINFO[0m] 
* 2023-06-07 02:18:29 (4119) [[32mINFO[0m] 
* 2023-06-07 02:18:29 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-07 02:18:29 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-07 02:18:29 (4089) [[32mINFO[0m] 
* 2023-06-07 02:18:30 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-07 02:18:31 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-07 02:18:31 (4119) [[32mINFO[0m] 
* 2023-06-07 02:19:20 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-07 02:19:20 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EagteYnKk9/ea_profile.json
* 2023-06-07 02:19:22 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/EagteYnKk9/ea_profile.json
* 2023-06-07 02:19:24 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-08 02:27:12 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-08 02:27:12 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-08 02:27:12 (4089) [[32mINFO[0m] 
* 2023-06-08 02:27:12 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-08 02:27:12 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-08 02:27:12 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-08 02:27:13 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-08 02:27:13 (4119) [[32mINFO[0m] 
* 2023-06-08 02:27:13 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-08 02:27:13 (4089) [[32mINFO[0m] 
* 2023-06-08 02:33:03 (4119) [[32mINFO[0m] 
* 2023-06-08 02:33:03 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-08 02:33:03 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-08 02:33:03 (4089) [[32mINFO[0m] 
* 2023-06-08 02:33:03 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-08 02:33:04 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-08 02:33:04 (4119) [[32mINFO[0m] 
* 2023-06-08 02:36:12 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-08 02:36:12 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pBuxYSO9w2/ea_profile.json
* 2023-06-08 02:36:14 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/pBuxYSO9w2/ea_profile.json
* 2023-06-08 02:36:17 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-09 02:20:09 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-09 02:20:09 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-09 02:20:09 (4089) [[32mINFO[0m] 
* 2023-06-09 02:20:09 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-09 02:20:09 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-09 02:20:09 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-09 02:20:09 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-09 02:20:09 (4119) [[32mINFO[0m] 
* 2023-06-09 02:20:09 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-09 02:20:09 (4089) [[32mINFO[0m] 
* 2023-06-09 02:21:03 (4102) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:21:03 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:03 (4102) [[32mINFO[0m] To address this issue please refer to the below wiki article 
* 2023-06-09 02:21:03 (4102) [[32mINFO[0m] 
* 2023-06-09 02:21:03 (4102) [[32mINFO[0m] https://wiki.centos.org/yum-errors
* 2023-06-09 02:21:03 (4102) [[32mINFO[0m] 
* 2023-06-09 02:21:03 (4102) [[32mINFO[0m] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2023-06-09 02:21:03 (4102) [[32mINFO[0m] 
* 2023-06-09 02:21:07 (4102) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:21:07 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:08 (4102) [[32mINFO[0m] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:21:08 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:12 (4102) [[32mINFO[0m] https://mirrors.thzhost.com/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:21:12 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:13 (4102) [[32mINFO[0m] http://mirror.earthlink.iq/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:21:13 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:15 (4102) [[32mINFO[0m] https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:21:15 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:18 (4102) [[32mINFO[0m] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:21:18 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:19 (4102) [[32mINFO[0m] https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:21:19 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:20 (4102) [[32mINFO[0m] https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:21:20 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:22 (4102) [[32mINFO[0m] https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:21:22 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:25 (4102) [[32mINFO[0m] https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:21:25 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:26 (4102) [[32mINFO[0m] https://mirrors.thzhost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:21:26 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:26 (4102) [[32mINFO[0m] http://mirror.earthlink.iq/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:21:26 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:29 (4102) [[32mINFO[0m] http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:21:29 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:30 (4102) [[32mINFO[0m] https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:21:30 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:37 (4102) [[32mINFO[0m] https://ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-projects/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:21:37 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:39 (4102) [[32mINFO[0m] https://repo.extreme-ix.org/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:21:39 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:44 (4102) [[32mINFO[0m] https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:21:44 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:45 (4102) [[32mINFO[0m] https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:21:45 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:47 (4102) [[32mINFO[0m] https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:21:47 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:49 (4102) [[32mINFO[0m] http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:21:49 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:49 (4102) [[32mINFO[0m] http://mirror2.totbb.net/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:21:49 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:50 (4102) [[32mINFO[0m] http://repo.ugm.ac.id/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:21:50 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:53 (4102) [[32mINFO[0m] https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:21:53 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:54 (4102) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 02:21:54 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:21:54 (4102) [[32mINFO[0m] It was impossible to connect to the CentOS servers.
* 2023-06-09 02:21:54 (4102) [[32mINFO[0m] This could mean a connectivity issue in your environment, such as the requirement to configure a proxy,
* 2023-06-09 02:21:54 (4102) [[32mINFO[0m] or a transparent proxy that tampers with TLS security, or an incorrect system clock.
* 2023-06-09 02:21:54 (4102) [[32mINFO[0m] You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors
* 2023-06-09 02:21:54 (4102) [[32mINFO[0m] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2023-06-09 02:21:54 (4102) [[32mINFO[0m] 
* 2023-06-09 02:21:55 (4102) [[32mINFO[0m] https://epel.excellmedia.net/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 02:21:55 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:22:00 (4102) [[32mINFO[0m] https://ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-projects/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:22:00 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:22:01 (4102) [[32mINFO[0m] http://repo.ugm.ac.id/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:22:01 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:22:02 (4102) [[32mINFO[0m] https://repo.extreme-ix.org/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:22:02 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:22:06 (4102) [[32mINFO[0m] https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:22:06 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:22:11 (4102) [[32mINFO[0m] http://mirror2.totbb.net/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:22:11 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:22:16 (4102) [[32mINFO[0m] https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:22:16 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:22:17 (4102) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 02:22:17 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:22:20 (4102) [[32mINFO[0m] https://epel.excellmedia.net/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 02:22:20 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:22:31 (4102) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:22:31 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:22:36 (4102) [[32mINFO[0m] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:22:36 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:22:39 (4102) [[32mINFO[0m] https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:22:39 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:22:48 (4102) [[32mINFO[0m] https://mirrors.thzhost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:22:48 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:22:49 (4102) [[32mINFO[0m] http://mirror.earthlink.iq/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:22:49 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:22:54 (4102) [[32mINFO[0m] https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:22:54 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:22:56 (4102) [[32mINFO[0m] https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:22:56 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:23:01 (4102) [[32mINFO[0m] https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:23:01 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:23:04 (4102) [[32mINFO[0m] http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:23:04 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:23:13 (4102) [[32mINFO[0m] https://ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-projects/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:23:13 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:23:15 (4102) [[32mINFO[0m] http://repo.ugm.ac.id/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:23:15 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:23:17 (4102) [[32mINFO[0m] https://repo.extreme-ix.org/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:23:17 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:23:26 (4102) [[32mINFO[0m] https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:23:26 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:23:30 (4102) [[32mINFO[0m] http://mirror2.totbb.net/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:23:30 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:23:47 (4102) [[32mINFO[0m] https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to mirrors.cqu.edu.cn:443; Operation now in progress"
* 2023-06-09 02:23:47 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:23:47 (4102) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 02:23:47 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:23:51 (4102) [[32mINFO[0m] https://epel.excellmedia.net/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 02:23:51 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:23:55 (4102) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:23:55 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:24:00 (4102) [[32mINFO[0m] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:24:00 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:24:02 (4102) [[32mINFO[0m] https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:24:02 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:24:11 (4102) [[32mINFO[0m] https://mirrors.thzhost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:24:11 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:24:12 (4102) [[32mINFO[0m] http://mirror.earthlink.iq/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:24:12 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:24:17 (4102) [[32mINFO[0m] https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:24:17 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:24:18 (4102) [[32mINFO[0m] https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:24:18 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:24:22 (4102) [[32mINFO[0m] https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:24:22 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:24:26 (4102) [[32mINFO[0m] http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:24:26 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:24:45 (4102) [[32mINFO[0m] https://ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-projects/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:24:45 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:24:54 (4102) [[32mINFO[0m] https://repo.extreme-ix.org/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:24:54 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:24:58 (4102) [[32mINFO[0m] https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:24:58 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:25:03 (4102) [[32mINFO[0m] http://mirror2.totbb.net/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:25:03 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:25:03 (4102) [[32mINFO[0m] http://repo.ugm.ac.id/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:25:03 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:25:20 (4102) [[32mINFO[0m] https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to mirrors.cqu.edu.cn:443; Success"
* 2023-06-09 02:25:20 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:25:20 (4102) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 02:25:20 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] https://epel.excellmedia.net/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] 
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] 
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]  One of the configured repositories failed (Extra Packages for Enterprise Linux 7 - x86_64),
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] 
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] 
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] 
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]             yum --disablerepo=epel ...
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] 
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] 
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]             yum-config-manager --disable epel
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]         or
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]             subscription-manager repos --disable=epel
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] 
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]         compromise:
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] 
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m]             yum-config-manager --save --setopt=epel.skip_if_unavailable=true
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] 
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] failure: repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2 from epel: [Errno 256] No more mirrors to try.
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] https://mirrors.thzhost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] http://mirror.earthlink.iq/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] https://ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-projects/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] https://repo.extreme-ix.org/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] http://mirror2.totbb.net/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] http://repo.ugm.ac.id/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to mirrors.cqu.edu.cn:443; Success"
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] https://epel.excellmedia.net/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 02:25:24 (4119) [[32mINFO[0m] 
* 2023-06-09 02:25:24 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-09 02:25:24 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-09 02:25:24 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-09 02:25:24 (4089) [[32mINFO[0m] 
* 2023-06-09 02:25:24 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-09 02:25:25 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-09 02:25:25 (4119) [[32mINFO[0m] 
* 2023-06-09 02:30:44 (1566) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-06-09 02:30:44 (1567) [[31mERROR[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.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/.

http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-projects/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://repo.ugm.ac.id/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://repo.ugm.ac.id/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-projects/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-projects/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://repo.ugm.ac.id/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://repo.ugm.ac.id/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirror2.totbb.net/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror2.totbb.net/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://repo.ugm.ac.id/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-projects/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror2.totbb.net/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-projects/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to mirrors.cqu.edu.cn:443; Operation now in progress"
Trying other mirror.
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] curl#7 - "Failed connect to mirrors.cqu.edu.cn:443; Operation now in progress"
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
It was impossible to connect to the CentOS servers.
This could mean a connectivity issue in your environment, such as the requirement to configure a proxy,
or a transparent proxy that tampers with TLS security, or an incorrect system clock.
You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors
If above article doesn't help to resolve this issue please use https://bugs.centos.org/.

https://repo.extreme-ix.org/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
http://mirror2.totbb.net/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
http://mirror2.totbb.net/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://repo.ugm.ac.id/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-projects/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://repo.ugm.ac.id/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-projects/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://repo.ugm.ac.id/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror2.totbb.net/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-projects/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror2.totbb.net/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
http://mirror2.totbb.net/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-projects/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://repo.ugm.ac.id/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror2.totbb.net/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.


 One of the configured repositories failed (Extra Packages for Enterprise Linux 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=epel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable epel
        or
            subscription-manager repos --disable=epel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=epel.skip_if_unavailable=true

failure: repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2 from epel: [Errno 256] No more mirrors to try.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
https://mirrors.thzhost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
http://mirror.earthlink.iq/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
https://download.nus.edu.sg/mirror/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
https://ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-projects/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
http://repo.ugm.ac.id/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
https://repo.extreme-ix.org/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
http://mirror2.totbb.net/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
https://epel.excellmedia.net/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 02:30:44 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-09 02:30:45 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-09 02:30:45 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ppfXosoWJ0/ea_profile.json
* 2023-06-09 02:35:18 (297) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ppfXosoWJ0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-09 02:35:18 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-09 15:58:47 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-09 15:58:47 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-09 15:58:47 (4089) [[32mINFO[0m] 
* 2023-06-09 15:58:47 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-09 15:58:47 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-09 15:58:47 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-09 15:58:47 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-09 15:58:48 (4119) [[32mINFO[0m] 
* 2023-06-09 15:58:48 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-09 15:58:48 (4089) [[32mINFO[0m] 
* 2023-06-09 15:59:51 (4102) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 15:59:51 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 15:59:51 (4102) [[32mINFO[0m] To address this issue please refer to the below wiki article 
* 2023-06-09 15:59:51 (4102) [[32mINFO[0m] 
* 2023-06-09 15:59:51 (4102) [[32mINFO[0m] https://wiki.centos.org/yum-errors
* 2023-06-09 15:59:51 (4102) [[32mINFO[0m] 
* 2023-06-09 15:59:51 (4102) [[32mINFO[0m] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2023-06-09 15:59:51 (4102) [[32mINFO[0m] 
* 2023-06-09 15:59:55 (4102) [[32mINFO[0m] https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 15:59:55 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 15:59:57 (4102) [[32mINFO[0m] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 15:59:57 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 15:59:59 (4102) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 15:59:59 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:01 (4102) [[32mINFO[0m] https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:00:01 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:02 (4102) [[32mINFO[0m] http://mirror.earthlink.iq/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 16:00:02 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:08 (4102) [[32mINFO[0m] https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:00:08 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:12 (4102) [[32mINFO[0m] https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:00:12 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:19 (4102) [[32mINFO[0m] http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 16:00:19 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:21 (4102) [[32mINFO[0m] https://repo.extreme-ix.org/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:00:21 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:29 (4102) [[32mINFO[0m] https://mirrors.thzhost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 12] Timeout on https://mirrors.thzhost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-06-09 16:00:29 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:34 (4102) [[32mINFO[0m] https://mirrors.thzhost.com/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:00:34 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:36 (4102) [[32mINFO[0m] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:00:36 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:36 (4102) [[32mINFO[0m] http://mirror.earthlink.iq/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 16:00:36 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:39 (4102) [[32mINFO[0m] https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:00:39 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:41 (4102) [[32mINFO[0m] https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:00:41 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:42 (4102) [[32mINFO[0m] https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:00:42 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:46 (4102) [[32mINFO[0m] http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 16:00:46 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:48 (4102) [[32mINFO[0m] https://repo.extreme-ix.org/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:00:48 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:49 (4102) [[32mINFO[0m] https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] curl#35 - "Encountered end of file"
* 2023-06-09 16:00:49 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:50 (4102) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 16:00:50 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:50 (4102) [[32mINFO[0m] It was impossible to connect to the CentOS servers.
* 2023-06-09 16:00:50 (4102) [[32mINFO[0m] This could mean a connectivity issue in your environment, such as the requirement to configure a proxy,
* 2023-06-09 16:00:50 (4102) [[32mINFO[0m] or a transparent proxy that tampers with TLS security, or an incorrect system clock.
* 2023-06-09 16:00:50 (4102) [[32mINFO[0m] You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors
* 2023-06-09 16:00:50 (4102) [[32mINFO[0m] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2023-06-09 16:00:50 (4102) [[32mINFO[0m] 
* 2023-06-09 16:00:52 (4102) [[32mINFO[0m] https://epel.excellmedia.net/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 16:00:52 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:00:59 (4102) [[32mINFO[0m] https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:00:59 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:01:07 (4102) [[32mINFO[0m] https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#52 - "Empty reply from server"
* 2023-06-09 16:01:07 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:01:08 (4102) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 16:01:08 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:01:11 (4102) [[32mINFO[0m] https://epel.excellmedia.net/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 16:01:11 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:01:22 (4102) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 16:01:22 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:01:27 (4102) [[32mINFO[0m] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:01:27 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:01:30 (4102) [[32mINFO[0m] https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:01:30 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:01:35 (4102) [[32mINFO[0m] https://mirrors.thzhost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:01:35 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:01:36 (4102) [[32mINFO[0m] http://mirror.earthlink.iq/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 16:01:36 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:01:43 (4102) [[32mINFO[0m] https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:01:44 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:01:45 (4102) [[32mINFO[0m] https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:01:45 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:01:49 (4102) [[32mINFO[0m] http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 16:01:49 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:01:51 (4102) [[32mINFO[0m] https://repo.extreme-ix.org/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:01:51 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:01:59 (4102) [[32mINFO[0m] https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:01:59 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:02:03 (4102) [[32mINFO[0m] https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:02:03 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:02:04 (4102) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 16:02:04 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:02:08 (4102) [[32mINFO[0m] https://epel.excellmedia.net/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 16:02:08 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:02:12 (4102) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 16:02:12 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:02:21 (4102) [[32mINFO[0m] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:02:21 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:02:28 (4102) [[32mINFO[0m] https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:02:28 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:02:33 (4102) [[32mINFO[0m] https://mirrors.thzhost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:02:33 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:02:34 (4102) [[32mINFO[0m] http://mirror.earthlink.iq/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 16:02:34 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:02:40 (4102) [[32mINFO[0m] https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:02:40 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:02:41 (4102) [[32mINFO[0m] https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:02:41 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:02:45 (4102) [[32mINFO[0m] http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 16:02:45 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:02:49 (4102) [[32mINFO[0m] https://repo.extreme-ix.org/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:02:49 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:02:56 (4102) [[32mINFO[0m] https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:02:56 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:03:01 (4102) [[32mINFO[0m] https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:03:01 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:03:01 (4102) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 16:03:01 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] https://epel.excellmedia.net/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] 
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] 
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]  One of the configured repositories failed (Extra Packages for Enterprise Linux 7 - x86_64),
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] 
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] 
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] 
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]             yum --disablerepo=epel ...
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] 
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] 
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]             yum-config-manager --disable epel
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]         or
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]             subscription-manager repos --disable=epel
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] 
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]         compromise:
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] 
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m]             yum-config-manager --save --setopt=epel.skip_if_unavailable=true
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] 
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] failure: repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2 from epel: [Errno 256] No more mirrors to try.
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] https://mirrors.thzhost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] http://mirror.earthlink.iq/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] https://repo.extreme-ix.org/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] https://epel.excellmedia.net/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 16:03:05 (4119) [[32mINFO[0m] 
* 2023-06-09 16:03:05 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-09 16:03:05 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-09 16:03:05 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-09 16:03:05 (4089) [[32mINFO[0m] 
* 2023-06-09 16:03:05 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-09 16:03:07 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-09 16:03:07 (4119) [[32mINFO[0m] 
* 2023-06-09 16:07:41 (1566) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-06-09 16:07:41 (1567) [[31mERROR[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.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/.

http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
It was impossible to connect to the CentOS servers.
This could mean a connectivity issue in your environment, such as the requirement to configure a proxy,
or a transparent proxy that tampers with TLS security, or an incorrect system clock.
You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors
If above article doesn't help to resolve this issue please use https://bugs.centos.org/.

https://repo.extreme-ix.org/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/0fc7ec79f23bd9143b722473a83a7aa13734c04c7ca3964cc2c80b7be55f3dfb-prestodelta.xml.gz: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
http://mirror.natro.com/centos/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on http://mirror.natro.com/centos/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/1cf2397cf4942717d6c8b3d24896d4d634c34986c81d1f031dc84cb7fb35485c-updateinfo.xml.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/15cece63371d5a0dd343c84f000eda95f020fd56dd87faadec293ea8016bb3ba-other.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/fad89ac1c7da434f7e843545cb327b1b43fb3b8b91dba071571fb494056db26a-filelists.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.thzhost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://mirror.earthlink.iq/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
https://repo.extreme-ix.org/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.
https://epel.excellmedia.net/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
Trying other mirror.


 One of the configured repositories failed (Extra Packages for Enterprise Linux 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=epel ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable epel
        or
            subscription-manager repos --disable=epel

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=epel.skip_if_unavailable=true

failure: repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2 from epel: [Errno 256] No more mirrors to try.
http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
https://mirror-icn.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
https://mirrors.thzhost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
http://mirror.earthlink.iq/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
https://mirror-hnd.yuki.net.uk/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
https://ftp.riken.jp/Linux/fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
http://ftp.iij.ad.jp/pub/linux/Fedora/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
https://repo.extreme-ix.org/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
https://mirrors.bestthaihost.com/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
https://mirrors.cqu.edu.cn/epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found
https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
https://epel.excellmedia.net/7/x86_64/repodata/e062d98924418311ea8d8da53806a0643e0134a51ea7480d6e77e5b732cb7bb1-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-06-09 16:07:41 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-09 16:07:42 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-09 16:07:42 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/R1ryu62ZWi/ea_profile.json
* 2023-06-09 16:14:07 (297) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/R1ryu62ZWi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238.
* 2023-06-09 16:14:07 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-10 02:17:02 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-06-10 02:17:03 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-10 02:17:03 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-10 02:17:03 (4089) [[32mINFO[0m] 
* 2023-06-10 02:17:04 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-10 02:17:04 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-10 02:17:04 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-10 02:17:04 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-10 02:17:04 (4119) [[32mINFO[0m] 
* 2023-06-10 02:17:04 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-10 02:17:04 (4089) [[32mINFO[0m] 
* 2023-06-10 02:18:11 (4119) [[32mINFO[0m] 
* 2023-06-10 02:18:11 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-10 02:18:11 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-10 02:18:11 (4089) [[32mINFO[0m] 
* 2023-06-10 02:18:11 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-10 02:18:12 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-10 02:18:12 (4119) [[32mINFO[0m] 
* 2023-06-10 02:19:05 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-10 02:19:05 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9xkFpXxvvL/ea_profile.json
* 2023-06-10 02:19:06 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/9xkFpXxvvL/ea_profile.json
* 2023-06-10 02:19:09 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-11 02:16:43 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-06-11 02:16:44 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-11 02:16:44 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-11 02:16:44 (4089) [[32mINFO[0m] 
* 2023-06-11 02:16:44 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-11 02:16:44 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-11 02:16:44 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-11 02:16:44 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-11 02:16:44 (4119) [[32mINFO[0m] 
* 2023-06-11 02:16:44 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-11 02:16:44 (4089) [[32mINFO[0m] 
* 2023-06-11 02:17:48 (4119) [[32mINFO[0m] 
* 2023-06-11 02:17:48 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-11 02:17:48 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-11 02:17:48 (4089) [[32mINFO[0m] 
* 2023-06-11 02:17:48 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-11 02:17:50 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-11 02:17:50 (4119) [[32mINFO[0m] 
* 2023-06-11 02:18:34 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-11 02:18:34 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KKj7vKJsAp/ea_profile.json
* 2023-06-11 02:18:36 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/KKj7vKJsAp/ea_profile.json
* 2023-06-11 02:18:39 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-12 02:19:24 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-12 02:19:24 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-12 02:19:24 (4089) [[32mINFO[0m] 
* 2023-06-12 02:19:24 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-12 02:19:24 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-12 02:19:24 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-12 02:19:24 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-12 02:19:24 (4119) [[32mINFO[0m] 
* 2023-06-12 02:19:24 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-12 02:19:24 (4089) [[32mINFO[0m] 
* 2023-06-12 02:25:13 (4102) [[32mINFO[0m] http://mirror.radoreservers.com/centos/7.9.2009/updates/x86_64/repodata/81d0644d1cd86a7d7b1d5a83959869ce30fe99f09d1bf8cedd23b9da182f2751-primary.sqlite.bz2: [Errno 12] Timeout on http://mirror.radoreservers.com/centos/7.9.2009/updates/x86_64/repodata/81d0644d1cd86a7d7b1d5a83959869ce30fe99f09d1bf8cedd23b9da182f2751-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-06-12 02:25:13 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-06-12 02:25:35 (4119) [[32mINFO[0m] 
* 2023-06-12 02:25:35 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-12 02:25:35 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-12 02:25:35 (4089) [[32mINFO[0m] 
* 2023-06-12 02:25:36 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-12 02:25:37 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-12 02:25:37 (4119) [[32mINFO[0m] 
* 2023-06-12 02:26:33 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-12 02:26:35 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aiIWH6OlOi/ea_profile.json
* 2023-06-12 02:26:36 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/aiIWH6OlOi/ea_profile.json
* 2023-06-12 02:26:46 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-13 02:19:33 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-13 02:19:33 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-13 02:19:33 (4089) [[32mINFO[0m] 
* 2023-06-13 02:19:34 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-13 02:19:34 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-13 02:19:34 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-13 02:19:34 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-13 02:19:34 (4119) [[32mINFO[0m] 
* 2023-06-13 02:19:34 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-13 02:19:34 (4089) [[32mINFO[0m] 
* 2023-06-13 02:25:33 (4119) [[32mINFO[0m] 
* 2023-06-13 02:25:33 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-13 02:25:33 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-13 02:25:33 (4089) [[32mINFO[0m] 
* 2023-06-13 02:25:33 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-13 02:25:34 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-13 02:25:34 (4119) [[32mINFO[0m] 
* 2023-06-13 02:26:28 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-13 02:26:31 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/59xUlItftl/ea_profile.json
* 2023-06-13 02:26:32 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/59xUlItftl/ea_profile.json
* 2023-06-13 02:26:35 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-14 02:17:18 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-14 02:17:18 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-14 02:17:18 (4089) [[32mINFO[0m] 
* 2023-06-14 02:17:18 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-14 02:17:18 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-14 02:17:18 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-14 02:17:18 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-14 02:17:18 (4119) [[32mINFO[0m] 
* 2023-06-14 02:17:18 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-14 02:17:18 (4089) [[32mINFO[0m] 
* 2023-06-14 02:21:54 (4119) [[32mINFO[0m] 
* 2023-06-14 02:21:54 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-14 02:21:54 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-14 02:21:54 (4089) [[32mINFO[0m] 
* 2023-06-14 02:21:54 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-14 02:21:56 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-14 02:21:56 (4119) [[32mINFO[0m] 
* 2023-06-14 02:22:43 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-14 02:22:43 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/P5Mv8mL7FE/ea_profile.json
* 2023-06-14 02:22:45 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/P5Mv8mL7FE/ea_profile.json
* 2023-06-14 02:22:48 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-15 02:18:24 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-15 02:18:24 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-15 02:18:24 (4089) [[32mINFO[0m] 
* 2023-06-15 02:18:24 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-15 02:18:24 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-15 02:18:24 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-15 02:18:25 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-15 02:18:25 (4119) [[32mINFO[0m] 
* 2023-06-15 02:18:25 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-15 02:18:25 (4089) [[32mINFO[0m] 
* 2023-06-15 02:19:22 (4119) [[32mINFO[0m] 
* 2023-06-15 02:19:22 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-15 02:19:22 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-15 02:19:22 (4089) [[32mINFO[0m] 
* 2023-06-15 02:19:22 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-15 02:19:24 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-15 02:19:24 (4119) [[32mINFO[0m] 
* 2023-06-15 02:20:06 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-15 02:20:06 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Mgu8nb7KAP/ea_profile.json
* 2023-06-15 02:20:08 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/Mgu8nb7KAP/ea_profile.json
* 2023-06-15 02:20:18 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-16 02:17:11 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-16 02:17:11 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-16 02:17:11 (4089) [[32mINFO[0m] 
* 2023-06-16 02:17:12 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-16 02:17:12 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-16 02:17:12 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-16 02:17:12 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-16 02:17:12 (4119) [[32mINFO[0m] 
* 2023-06-16 02:17:12 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-16 02:17:12 (4089) [[32mINFO[0m] 
* 2023-06-16 02:18:14 (4119) [[32mINFO[0m] 
* 2023-06-16 02:18:14 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-16 02:18:14 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-16 02:18:14 (4089) [[32mINFO[0m] 
* 2023-06-16 02:18:15 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-16 02:18:16 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-16 02:18:16 (4119) [[32mINFO[0m] 
* 2023-06-16 02:19:02 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-16 02:19:02 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xL8ifEzmZ9/ea_profile.json
* 2023-06-16 02:19:04 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/xL8ifEzmZ9/ea_profile.json
* 2023-06-16 02:19:07 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-16 15:51:28 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-16 15:51:28 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-16 15:51:28 (4089) [[32mINFO[0m] 
* 2023-06-16 15:51:28 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-16 15:51:28 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-16 15:51:28 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-16 15:51:28 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-16 15:51:29 (4119) [[32mINFO[0m] 
* 2023-06-16 15:51:29 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-16 15:51:29 (4089) [[32mINFO[0m] 
* 2023-06-16 15:53:40 (4119) [[32mINFO[0m] 
* 2023-06-16 15:53:40 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-16 15:53:40 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-16 15:53:40 (4089) [[32mINFO[0m] 
* 2023-06-16 15:53:41 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-16 15:53:42 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-16 15:53:42 (4119) [[32mINFO[0m] 
* 2023-06-16 15:54:27 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-16 15:54:27 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oCHhIgviXr/ea_profile.json
* 2023-06-16 15:54:29 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/oCHhIgviXr/ea_profile.json
* 2023-06-16 15:54:32 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-17 02:16:25 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-06-17 02:16:26 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-17 02:16:26 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-17 02:16:26 (4089) [[32mINFO[0m] 
* 2023-06-17 02:16:27 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-17 02:16:27 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-17 02:16:27 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-17 02:16:27 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-17 02:16:27 (4119) [[32mINFO[0m] 
* 2023-06-17 02:16:27 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-17 02:16:27 (4089) [[32mINFO[0m] 
* 2023-06-17 02:17:30 (4119) [[32mINFO[0m] 
* 2023-06-17 02:17:30 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-17 02:17:30 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-17 02:17:30 (4089) [[32mINFO[0m] 
* 2023-06-17 02:17:31 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-17 02:17:32 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-17 02:17:32 (4119) [[32mINFO[0m] 
* 2023-06-17 02:18:16 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-17 02:18:16 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ta2YbINwWE/ea_profile.json
* 2023-06-17 02:18:18 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/Ta2YbINwWE/ea_profile.json
* 2023-06-17 02:18:21 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-18 02:16:43 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-06-18 02:16:43 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-18 02:16:43 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-18 02:16:43 (4089) [[32mINFO[0m] 
* 2023-06-18 02:16:44 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-18 02:16:44 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-18 02:16:44 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-18 02:16:44 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-18 02:16:44 (4119) [[32mINFO[0m] 
* 2023-06-18 02:16:44 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-18 02:16:44 (4089) [[32mINFO[0m] 
* 2023-06-18 02:17:47 (4119) [[32mINFO[0m] 
* 2023-06-18 02:17:47 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-18 02:17:47 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-18 02:17:47 (4089) [[32mINFO[0m] 
* 2023-06-18 02:17:47 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-18 02:17:48 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-18 02:17:48 (4119) [[32mINFO[0m] 
* 2023-06-18 02:18:33 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-18 02:18:33 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SYn03vQrkS/ea_profile.json
* 2023-06-18 02:18:34 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/SYn03vQrkS/ea_profile.json
* 2023-06-18 02:18:36 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-19 02:18:06 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-19 02:18:06 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-19 02:18:06 (4089) [[32mINFO[0m] 
* 2023-06-19 02:18:06 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-19 02:18:07 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-19 02:18:07 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-19 02:18:07 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-19 02:18:07 (4119) [[32mINFO[0m] 
* 2023-06-19 02:18:07 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-19 02:18:07 (4089) [[32mINFO[0m] 
* 2023-06-19 02:19:17 (4119) [[32mINFO[0m] 
* 2023-06-19 02:19:17 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-19 02:19:17 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-19 02:19:17 (4089) [[32mINFO[0m] 
* 2023-06-19 02:19:18 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-19 02:19:19 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-19 02:19:19 (4119) [[32mINFO[0m] 
* 2023-06-19 02:20:07 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-19 02:20:07 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mUpyP_PI4e/ea_profile.json
* 2023-06-19 02:20:09 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/mUpyP_PI4e/ea_profile.json
* 2023-06-19 02:20:12 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-20 02:19:23 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-20 02:19:23 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-20 02:19:23 (4089) [[32mINFO[0m] 
* 2023-06-20 02:19:23 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-20 02:19:23 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-20 02:19:23 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-20 02:19:23 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-20 02:19:23 (4119) [[32mINFO[0m] 
* 2023-06-20 02:19:23 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-20 02:19:23 (4089) [[32mINFO[0m] 
* 2023-06-20 02:20:34 (4119) [[32mINFO[0m] 
* 2023-06-20 02:20:34 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-20 02:20:34 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-20 02:20:34 (4089) [[32mINFO[0m] 
* 2023-06-20 02:20:34 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-20 02:20:35 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-20 02:20:35 (4119) [[32mINFO[0m] 
* 2023-06-20 02:21:19 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-20 02:21:19 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/d1AIXQuuO7/ea_profile.json
* 2023-06-20 02:21:21 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/d1AIXQuuO7/ea_profile.json
* 2023-06-20 02:21:24 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-21 02:16:03 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-21 02:16:03 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-21 02:16:03 (4089) [[32mINFO[0m] 
* 2023-06-21 02:16:04 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-21 02:16:04 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-21 02:16:04 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-21 02:16:04 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-21 02:16:04 (4119) [[32mINFO[0m] 
* 2023-06-21 02:16:04 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-21 02:16:04 (4089) [[32mINFO[0m] 
* 2023-06-21 02:18:37 (4119) [[32mINFO[0m] 
* 2023-06-21 02:18:37 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-21 02:18:37 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-21 02:18:37 (4089) [[32mINFO[0m] 
* 2023-06-21 02:18:37 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-21 02:18:39 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-21 02:18:39 (4119) [[32mINFO[0m] 
* 2023-06-21 02:19:22 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-21 02:19:22 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/m8jqkmIS_B/ea_profile.json
* 2023-06-21 02:19:23 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/m8jqkmIS_B/ea_profile.json
* 2023-06-21 02:19:26 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-22 02:15:46 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-22 02:15:46 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-22 02:15:46 (4089) [[32mINFO[0m] 
* 2023-06-22 02:15:47 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-22 02:15:47 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-22 02:15:47 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-22 02:15:47 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-22 02:15:47 (4119) [[32mINFO[0m] 
* 2023-06-22 02:15:47 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-22 02:15:47 (4089) [[32mINFO[0m] 
* 2023-06-22 02:16:48 (4119) [[32mINFO[0m] 
* 2023-06-22 02:16:48 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-22 02:16:48 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-22 02:16:48 (4089) [[32mINFO[0m] 
* 2023-06-22 02:16:49 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-22 02:16:50 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-22 02:16:50 (4119) [[32mINFO[0m] 
* 2023-06-22 02:17:37 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-22 02:17:37 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZdG1F0ouqw/ea_profile.json
* 2023-06-22 02:17:38 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/ZdG1F0ouqw/ea_profile.json
* 2023-06-22 02:17:40 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-23 02:16:05 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-23 02:16:05 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-23 02:16:05 (4089) [[32mINFO[0m] 
* 2023-06-23 02:16:05 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-23 02:16:05 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-23 02:16:05 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-23 02:16:05 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-23 02:16:05 (4119) [[32mINFO[0m] 
* 2023-06-23 02:16:05 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-23 02:16:05 (4089) [[32mINFO[0m] 
* 2023-06-23 02:21:11 (4119) [[32mINFO[0m] 
* 2023-06-23 02:21:11 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-23 02:21:11 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-23 02:21:11 (4089) [[32mINFO[0m] 
* 2023-06-23 02:21:11 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-23 02:21:14 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-23 02:21:14 (4119) [[32mINFO[0m] 
* 2023-06-23 02:22:18 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-23 02:22:22 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GXq_o8VQYe/ea_profile.json
* 2023-06-23 02:22:24 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/GXq_o8VQYe/ea_profile.json
* 2023-06-23 02:22:27 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-23 16:00:01 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-23 16:00:01 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-23 16:00:01 (4089) [[32mINFO[0m] 
* 2023-06-23 16:00:02 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-23 16:00:02 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-23 16:00:02 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-23 16:00:02 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-23 16:00:02 (4119) [[32mINFO[0m] 
* 2023-06-23 16:00:02 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-23 16:00:02 (4089) [[32mINFO[0m] 
* 2023-06-23 16:07:20 (4119) [[32mINFO[0m] 
* 2023-06-23 16:07:20 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-23 16:07:20 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-23 16:07:20 (4089) [[32mINFO[0m] 
* 2023-06-23 16:07:20 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-23 16:07:22 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-23 16:07:22 (4119) [[32mINFO[0m] 
* 2023-06-23 16:09:47 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-23 16:09:47 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tRef29JLxs/ea_profile.json
* 2023-06-23 16:09:49 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/tRef29JLxs/ea_profile.json
* 2023-06-23 16:09:52 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-24 02:16:33 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-06-24 02:16:34 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-24 02:16:34 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-24 02:16:34 (4089) [[32mINFO[0m] 
* 2023-06-24 02:16:34 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-24 02:16:34 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-24 02:16:34 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-24 02:16:35 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-24 02:16:35 (4119) [[32mINFO[0m] 
* 2023-06-24 02:16:35 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-24 02:16:35 (4089) [[32mINFO[0m] 
* 2023-06-24 02:23:09 (4119) [[32mINFO[0m] 
* 2023-06-24 02:23:09 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-24 02:23:09 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-24 02:23:09 (4089) [[32mINFO[0m] 
* 2023-06-24 02:23:10 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-24 02:23:11 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-24 02:23:11 (4119) [[32mINFO[0m] 
* 2023-06-24 02:24:00 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-24 02:24:00 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/V13llmdJi_/ea_profile.json
* 2023-06-24 02:24:02 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/V13llmdJi_/ea_profile.json
* 2023-06-24 02:24:05 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-25 02:15:56 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-25 02:15:56 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-25 02:15:56 (4089) [[32mINFO[0m] 
* 2023-06-25 02:15:56 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-25 02:15:56 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-25 02:15:56 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-25 02:15:57 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-25 02:15:57 (4119) [[32mINFO[0m] 
* 2023-06-25 02:15:57 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-25 02:15:57 (4089) [[32mINFO[0m] 
* 2023-06-25 02:16:52 (4119) [[32mINFO[0m] 
* 2023-06-25 02:16:52 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-25 02:16:52 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-25 02:16:52 (4089) [[32mINFO[0m] 
* 2023-06-25 02:16:53 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-25 02:16:54 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-25 02:16:54 (4119) [[32mINFO[0m] 
* 2023-06-25 02:17:40 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-25 02:17:40 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KUYI9dbVF2/ea_profile.json
* 2023-06-25 02:17:42 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/KUYI9dbVF2/ea_profile.json
* 2023-06-25 02:17:45 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-26 02:15:50 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-26 02:15:50 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-26 02:15:50 (4089) [[32mINFO[0m] 
* 2023-06-26 02:15:50 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-26 02:15:50 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-26 02:15:50 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-26 02:15:50 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-26 02:15:50 (4119) [[32mINFO[0m] 
* 2023-06-26 02:15:50 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-26 02:15:50 (4089) [[32mINFO[0m] 
* 2023-06-26 02:16:56 (4119) [[32mINFO[0m] 
* 2023-06-26 02:16:56 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-06-26 02:16:56 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-06-26 02:16:56 (4089) [[32mINFO[0m] 
* 2023-06-26 02:16:57 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-26 02:16:58 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-06-26 02:16:58 (4119) [[32mINFO[0m] 
* 2023-06-26 02:17:40 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-26 02:17:41 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TJ5v5zRTc6/ea_profile.json
* 2023-06-26 02:17:42 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/TJ5v5zRTc6/ea_profile.json
* 2023-06-26 02:17:45 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-06-27 02:16:40 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-06-27 02:16:43 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-27 02:16:43 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-27 02:16:43 (4089) [[32mINFO[0m] 
* 2023-06-27 02:16:43 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-27 02:16:43 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-27 02:16:44 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-27 02:16:44 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-27 02:16:44 (4119) [[32mINFO[0m] 
* 2023-06-27 02:16:44 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-27 02:16:44 (4089) [[32mINFO[0m] 
* 2023-06-27 02:17:54 (4102) [[32mINFO[0m] 
* 2023-06-27 02:17:54 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-06-27 02:17:55 (4119) [[32mINFO[0m] 
* 2023-06-27 02:17:55 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-27 02:17:55 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-27 02:18:56 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-27 02:18:56 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fXtaTbp6DN/ea_profile.json
* 2023-06-27 02:18:58 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/fXtaTbp6DN/ea_profile.json
* 2023-06-27 02:19:09 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-28 02:15:07 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-28 02:15:07 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-28 02:15:07 (4089) [[32mINFO[0m] 
* 2023-06-28 02:15:08 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-28 02:15:08 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-28 02:15:08 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-28 02:15:08 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-28 02:15:08 (4119) [[32mINFO[0m] 
* 2023-06-28 02:15:08 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-28 02:15:08 (4089) [[32mINFO[0m] 
* 2023-06-28 02:16:05 (4102) [[32mINFO[0m] 
* 2023-06-28 02:16:05 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-06-28 02:16:06 (4119) [[32mINFO[0m] 
* 2023-06-28 02:16:06 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-28 02:16:06 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-28 02:16:49 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-28 02:16:49 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BdUocfaTq6/ea_profile.json
* 2023-06-28 02:16:51 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/BdUocfaTq6/ea_profile.json
* 2023-06-28 02:16:54 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-29 02:15:20 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-29 02:15:20 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-29 02:15:20 (4089) [[32mINFO[0m] 
* 2023-06-29 02:15:20 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-29 02:15:20 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-29 02:15:20 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-29 02:15:21 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-29 02:15:21 (4119) [[32mINFO[0m] 
* 2023-06-29 02:15:21 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-29 02:15:21 (4089) [[32mINFO[0m] 
* 2023-06-29 02:16:16 (4102) [[32mINFO[0m] 
* 2023-06-29 02:16:16 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-06-29 02:16:16 (4119) [[32mINFO[0m] 
* 2023-06-29 02:16:16 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-29 02:16:16 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-29 02:16:58 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-29 02:16:58 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/o5KkH5dnLZ/ea_profile.json
* 2023-06-29 02:17:00 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/o5KkH5dnLZ/ea_profile.json
* 2023-06-29 02:17:03 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-30 02:15:28 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-30 02:15:28 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-30 02:15:28 (4089) [[32mINFO[0m] 
* 2023-06-30 02:15:28 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-30 02:15:28 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-30 02:15:28 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-30 02:15:29 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-30 02:15:29 (4119) [[32mINFO[0m] 
* 2023-06-30 02:15:29 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-30 02:15:29 (4089) [[32mINFO[0m] 
* 2023-06-30 02:16:27 (4102) [[32mINFO[0m] 
* 2023-06-30 02:16:27 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-06-30 02:16:27 (4119) [[32mINFO[0m] 
* 2023-06-30 02:16:27 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-30 02:16:27 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-30 02:17:09 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-30 02:17:09 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AMB_gyQ3Bt/ea_profile.json
* 2023-06-30 02:17:10 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/AMB_gyQ3Bt/ea_profile.json
* 2023-06-30 02:17:13 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-30 15:50:27 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-06-30 15:50:27 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-06-30 15:50:27 (4089) [[32mINFO[0m] 
* 2023-06-30 15:50:27 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-30 15:50:27 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-06-30 15:50:27 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-06-30 15:50:27 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-06-30 15:50:27 (4119) [[32mINFO[0m] 
* 2023-06-30 15:50:27 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-06-30 15:50:27 (4089) [[32mINFO[0m] 
* 2023-06-30 15:51:29 (4102) [[32mINFO[0m] 
* 2023-06-30 15:51:29 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-06-30 15:51:29 (4119) [[32mINFO[0m] 
* 2023-06-30 15:51:29 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-30 15:51:29 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-30 15:52:40 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-30 15:52:40 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4to025fGX7/ea_profile.json
* 2023-06-30 15:52:42 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/4to025fGX7/ea_profile.json
* 2023-06-30 15:52:45 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-01 02:15:49 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-01 02:15:49 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-01 02:15:49 (4089) [[32mINFO[0m] 
* 2023-07-01 02:15:50 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-01 02:15:50 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-01 02:15:50 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-01 02:15:50 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-01 02:15:50 (4119) [[32mINFO[0m] 
* 2023-07-01 02:15:50 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-01 02:15:50 (4089) [[32mINFO[0m] 
* 2023-07-01 02:16:49 (4102) [[32mINFO[0m] 
* 2023-07-01 02:16:49 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-01 02:16:49 (4119) [[32mINFO[0m] 
* 2023-07-01 02:16:49 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-01 02:16:49 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-01 02:17:39 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-01 02:17:39 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LVNQenfoOC/ea_profile.json
* 2023-07-01 02:17:40 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/LVNQenfoOC/ea_profile.json
* 2023-07-01 02:17:43 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-02 02:15:40 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-02 02:15:40 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-02 02:15:40 (4089) [[32mINFO[0m] 
* 2023-07-02 02:15:40 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-02 02:15:40 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-02 02:15:40 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-02 02:15:40 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-02 02:15:40 (4119) [[32mINFO[0m] 
* 2023-07-02 02:15:40 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-02 02:15:40 (4089) [[32mINFO[0m] 
* 2023-07-02 02:16:38 (4102) [[32mINFO[0m] 
* 2023-07-02 02:16:38 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-02 02:16:38 (4119) [[32mINFO[0m] 
* 2023-07-02 02:16:38 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-02 02:16:38 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-02 02:17:20 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-02 02:17:20 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RdMEj5HOgN/ea_profile.json
* 2023-07-02 02:17:21 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/RdMEj5HOgN/ea_profile.json
* 2023-07-02 02:17:25 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-03 02:13:34 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-03 02:13:34 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-03 02:13:34 (4089) [[32mINFO[0m] 
* 2023-07-03 02:13:34 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-03 02:13:34 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-03 02:13:34 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-03 02:13:34 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-03 02:13:34 (4119) [[32mINFO[0m] 
* 2023-07-03 02:13:34 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-03 02:13:34 (4089) [[32mINFO[0m] 
* 2023-07-03 02:14:07 (4102) [[32mINFO[0m] 
* 2023-07-03 02:14:07 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-03 02:14:07 (4119) [[32mINFO[0m] 
* 2023-07-03 02:14:07 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-03 02:14:07 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-03 02:14:28 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-03 02:14:28 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8c6wc8xiHe/ea_profile.json
* 2023-07-03 02:14:30 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/8c6wc8xiHe/ea_profile.json
* 2023-07-03 02:14:34 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-04 02:14:47 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-04 02:14:47 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-04 02:14:47 (4089) [[32mINFO[0m] 
* 2023-07-04 02:14:47 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-04 02:14:48 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-04 02:14:48 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-04 02:14:48 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-04 02:14:48 (4119) [[32mINFO[0m] 
* 2023-07-04 02:14:48 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-04 02:14:48 (4089) [[32mINFO[0m] 
* 2023-07-04 02:15:41 (4102) [[32mINFO[0m] https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
* 2023-07-04 02:15:41 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-07-04 02:16:02 (4102) [[32mINFO[0m] 
* 2023-07-04 02:16:02 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-04 02:16:02 (4119) [[32mINFO[0m] 
* 2023-07-04 02:16:02 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-04 02:16:02 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-04 02:16:23 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-04 02:16:23 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/c61NStvWV9/ea_profile.json
* 2023-07-04 02:16:25 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/c61NStvWV9/ea_profile.json
* 2023-07-04 02:16:32 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-05 02:20:00 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-05 02:20:00 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-05 02:20:00 (4089) [[32mINFO[0m] 
* 2023-07-05 02:20:00 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-05 02:20:00 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-05 02:20:00 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-05 02:20:01 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-05 02:20:01 (4119) [[32mINFO[0m] 
* 2023-07-05 02:20:01 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-05 02:20:01 (4089) [[32mINFO[0m] 
* 2023-07-05 02:22:20 (4102) [[32mINFO[0m] 
* 2023-07-05 02:22:20 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-05 02:22:20 (4119) [[32mINFO[0m] 
* 2023-07-05 02:22:20 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-05 02:22:20 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-05 02:23:45 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-05 02:23:45 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wgkSsMGNi6/ea_profile.json
* 2023-07-05 02:23:46 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/wgkSsMGNi6/ea_profile.json
* 2023-07-05 02:23:49 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-06 02:15:52 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-06 02:15:52 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-06 02:15:52 (4089) [[32mINFO[0m] 
* 2023-07-06 02:15:52 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-06 02:15:52 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-06 02:15:52 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-06 02:15:52 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-06 02:15:52 (4119) [[32mINFO[0m] 
* 2023-07-06 02:15:52 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-06 02:15:52 (4089) [[32mINFO[0m] 
* 2023-07-06 02:16:48 (4102) [[32mINFO[0m] 
* 2023-07-06 02:16:48 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-06 02:16:49 (4119) [[32mINFO[0m] 
* 2023-07-06 02:16:49 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-06 02:16:49 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-06 02:17:40 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-06 02:17:40 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/X2RMH6eL7L/ea_profile.json
* 2023-07-06 02:17:42 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/X2RMH6eL7L/ea_profile.json
* 2023-07-06 02:17:45 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-07 02:15:13 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-07 02:15:13 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-07 02:15:13 (4089) [[32mINFO[0m] 
* 2023-07-07 02:15:13 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-07 02:15:13 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-07 02:15:13 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-07 02:15:13 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-07 02:15:13 (4119) [[32mINFO[0m] 
* 2023-07-07 02:15:13 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-07 02:15:13 (4089) [[32mINFO[0m] 
* 2023-07-07 02:16:06 (4102) [[32mINFO[0m] 
* 2023-07-07 02:16:06 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-07 02:16:07 (4119) [[32mINFO[0m] 
* 2023-07-07 02:16:07 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-07 02:16:07 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-07 02:16:57 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-07 02:16:57 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mv79QMmLTM/ea_profile.json
* 2023-07-07 02:16:59 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/mv79QMmLTM/ea_profile.json
* 2023-07-07 02:17:02 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-07 15:57:57 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-07 15:57:57 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-07 15:57:57 (4089) [[32mINFO[0m] 
* 2023-07-07 15:57:57 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-07 15:57:57 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-07 15:57:57 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-07 15:57:58 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-07 15:57:58 (4119) [[32mINFO[0m] 
* 2023-07-07 15:57:58 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-07 15:57:58 (4089) [[32mINFO[0m] 
* 2023-07-07 15:59:42 (4102) [[32mINFO[0m] 
* 2023-07-07 15:59:42 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-07 15:59:42 (4119) [[32mINFO[0m] 
* 2023-07-07 15:59:42 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-07 15:59:42 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-07 16:00:57 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-07 16:00:57 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/kr4IYjyESL/ea_profile.json
* 2023-07-07 16:00:59 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/kr4IYjyESL/ea_profile.json
* 2023-07-07 16:01:02 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-08 02:16:20 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-07-08 02:16:21 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-08 02:16:21 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-08 02:16:21 (4089) [[32mINFO[0m] 
* 2023-07-08 02:16:21 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-08 02:16:21 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-08 02:16:21 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-08 02:16:21 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-08 02:16:21 (4119) [[32mINFO[0m] 
* 2023-07-08 02:16:21 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-08 02:16:21 (4089) [[32mINFO[0m] 
* 2023-07-08 02:17:37 (4102) [[32mINFO[0m] 
* 2023-07-08 02:17:37 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-08 02:17:37 (4119) [[32mINFO[0m] 
* 2023-07-08 02:17:37 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-08 02:17:37 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-08 02:18:25 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-08 02:18:25 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/br5bVF5zvt/ea_profile.json
* 2023-07-08 02:18:27 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/br5bVF5zvt/ea_profile.json
* 2023-07-08 02:18:30 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-09 02:15:47 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-09 02:15:47 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-09 02:15:47 (4089) [[32mINFO[0m] 
* 2023-07-09 02:15:48 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-09 02:15:48 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-09 02:15:48 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-09 02:15:49 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-09 02:15:49 (4119) [[32mINFO[0m] 
* 2023-07-09 02:15:49 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-09 02:15:49 (4089) [[32mINFO[0m] 
* 2023-07-09 02:16:52 (4102) [[32mINFO[0m] 
* 2023-07-09 02:16:52 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-09 02:16:52 (4119) [[32mINFO[0m] 
* 2023-07-09 02:16:52 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-09 02:16:52 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-09 02:17:34 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-09 02:17:34 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mBrWtm_W11/ea_profile.json
* 2023-07-09 02:17:35 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/mBrWtm_W11/ea_profile.json
* 2023-07-09 02:17:39 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-10 02:13:30 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-10 02:13:30 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-10 02:13:30 (4089) [[32mINFO[0m] 
* 2023-07-10 02:13:31 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-10 02:13:31 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-10 02:13:31 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-10 02:13:31 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-10 02:13:31 (4119) [[32mINFO[0m] 
* 2023-07-10 02:13:31 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-10 02:13:31 (4089) [[32mINFO[0m] 
* 2023-07-10 02:14:00 (4102) [[32mINFO[0m] 
* 2023-07-10 02:14:00 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-10 02:14:00 (4119) [[32mINFO[0m] 
* 2023-07-10 02:14:00 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-10 02:14:00 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-10 02:14:22 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-10 02:14:24 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ju_jLIde2a/ea_profile.json
* 2023-07-10 02:14:27 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/ju_jLIde2a/ea_profile.json
* 2023-07-10 02:14:30 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-11 02:14:13 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-11 02:14:13 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-11 02:14:13 (4089) [[32mINFO[0m] 
* 2023-07-11 02:14:13 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-11 02:14:14 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-11 02:14:14 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-11 02:14:14 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-11 02:14:14 (4119) [[32mINFO[0m] 
* 2023-07-11 02:14:14 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-11 02:14:14 (4089) [[32mINFO[0m] 
* 2023-07-11 02:14:42 (4102) [[32mINFO[0m] 
* 2023-07-11 02:14:42 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-11 02:14:42 (4119) [[32mINFO[0m] 
* 2023-07-11 02:14:42 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-11 02:14:42 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-11 02:15:03 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-11 02:15:03 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/CkkvFMLrTv/ea_profile.json
* 2023-07-11 02:15:05 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/CkkvFMLrTv/ea_profile.json
* 2023-07-11 02:15:11 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-12 02:14:08 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-12 02:14:08 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-12 02:14:08 (4089) [[32mINFO[0m] 
* 2023-07-12 02:14:08 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-12 02:14:08 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-12 02:14:08 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-12 02:14:08 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-12 02:14:08 (4119) [[32mINFO[0m] 
* 2023-07-12 02:14:08 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-12 02:14:08 (4089) [[32mINFO[0m] 
* 2023-07-12 02:14:49 (4102) [[32mINFO[0m] 
* 2023-07-12 02:14:49 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-12 02:14:49 (4119) [[32mINFO[0m] 
* 2023-07-12 02:14:49 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-12 02:14:49 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-12 02:15:38 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-12 02:15:39 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7yjXj5cyt5/ea_profile.json
* 2023-07-12 02:15:40 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/7yjXj5cyt5/ea_profile.json
* 2023-07-12 02:15:43 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-13 02:18:29 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-13 02:18:29 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-13 02:18:29 (4089) [[32mINFO[0m] 
* 2023-07-13 02:18:29 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-13 02:18:29 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-13 02:18:29 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-13 02:18:29 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-13 02:18:29 (4119) [[32mINFO[0m] 
* 2023-07-13 02:18:29 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-13 02:18:29 (4089) [[32mINFO[0m] 
* 2023-07-13 02:19:30 (4102) [[32mINFO[0m] 
* 2023-07-13 02:19:30 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-13 02:19:31 (4119) [[32mINFO[0m] 
* 2023-07-13 02:19:31 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-13 02:19:31 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-13 02:20:11 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-13 02:20:11 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Pw4TyqC3Ug/ea_profile.json
* 2023-07-13 02:20:13 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/Pw4TyqC3Ug/ea_profile.json
* 2023-07-13 02:20:16 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-14 02:19:44 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-14 02:19:44 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-14 02:19:44 (4089) [[32mINFO[0m] 
* 2023-07-14 02:19:45 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-14 02:19:45 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-14 02:19:45 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-14 02:19:45 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-14 02:19:45 (4119) [[32mINFO[0m] 
* 2023-07-14 02:19:45 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-14 02:19:45 (4089) [[32mINFO[0m] 
* 2023-07-14 02:20:52 (4102) [[32mINFO[0m] 
* 2023-07-14 02:20:52 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-14 02:20:52 (4119) [[32mINFO[0m] 
* 2023-07-14 02:20:52 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-14 02:20:52 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-14 02:21:36 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-14 02:21:36 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hfLdYkeUvF/ea_profile.json
* 2023-07-14 02:21:38 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/hfLdYkeUvF/ea_profile.json
* 2023-07-14 02:21:41 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-14 16:12:48 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-14 16:12:48 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-14 16:12:48 (4089) [[32mINFO[0m] 
* 2023-07-14 16:12:48 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-14 16:12:49 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-14 16:12:49 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-14 16:12:49 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-14 16:12:49 (4119) [[32mINFO[0m] 
* 2023-07-14 16:12:49 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-14 16:12:49 (4089) [[32mINFO[0m] 
* 2023-07-14 16:13:59 (4102) [[32mINFO[0m] 
* 2023-07-14 16:13:59 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-14 16:13:59 (4119) [[32mINFO[0m] 
* 2023-07-14 16:13:59 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-14 16:13:59 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-14 16:16:24 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-14 16:16:24 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/X9mnr7J9cB/ea_profile.json
* 2023-07-14 16:16:25 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/X9mnr7J9cB/ea_profile.json
* 2023-07-14 16:16:28 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-15 02:15:48 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-15 02:15:48 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-15 02:15:48 (4089) [[32mINFO[0m] 
* 2023-07-15 02:15:48 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-15 02:15:48 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-15 02:15:48 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-15 02:15:49 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-15 02:15:49 (4119) [[32mINFO[0m] 
* 2023-07-15 02:15:49 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-15 02:15:49 (4089) [[32mINFO[0m] 
* 2023-07-15 02:16:45 (4102) [[32mINFO[0m] 
* 2023-07-15 02:16:45 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-15 02:16:45 (4119) [[32mINFO[0m] 
* 2023-07-15 02:16:45 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-15 02:16:45 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-15 02:17:24 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-15 02:17:24 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DBXQQAHsyQ/ea_profile.json
* 2023-07-15 02:17:26 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/DBXQQAHsyQ/ea_profile.json
* 2023-07-15 02:17:29 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-16 02:15:53 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-16 02:15:53 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-16 02:15:53 (4089) [[32mINFO[0m] 
* 2023-07-16 02:15:53 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-16 02:15:53 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-16 02:15:53 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-16 02:15:54 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-16 02:15:54 (4119) [[32mINFO[0m] 
* 2023-07-16 02:15:54 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-16 02:15:54 (4089) [[32mINFO[0m] 
* 2023-07-16 02:17:05 (4102) [[32mINFO[0m] 
* 2023-07-16 02:17:05 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-16 02:17:05 (4119) [[32mINFO[0m] 
* 2023-07-16 02:17:05 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-16 02:17:05 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-16 02:17:45 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-16 02:17:45 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/io0YDUO5Lh/ea_profile.json
* 2023-07-16 02:17:47 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/io0YDUO5Lh/ea_profile.json
* 2023-07-16 02:17:50 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-17 02:13:52 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-17 02:13:52 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-17 02:13:52 (4089) [[32mINFO[0m] 
* 2023-07-17 02:13:52 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-17 02:13:52 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-17 02:13:52 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-17 02:13:52 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-17 02:13:52 (4119) [[32mINFO[0m] 
* 2023-07-17 02:13:52 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-17 02:13:52 (4089) [[32mINFO[0m] 
* 2023-07-17 02:14:24 (4102) [[32mINFO[0m] 
* 2023-07-17 02:14:24 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-17 02:14:24 (4119) [[32mINFO[0m] 
* 2023-07-17 02:14:24 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-17 02:14:24 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-17 02:14:46 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-17 02:14:47 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TnoBer46Xe/ea_profile.json
* 2023-07-17 02:14:48 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/TnoBer46Xe/ea_profile.json
* 2023-07-17 02:14:51 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-18 02:13:42 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-18 02:13:42 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-18 02:13:42 (4089) [[32mINFO[0m] 
* 2023-07-18 02:13:43 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-18 02:13:43 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-18 02:13:43 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-18 02:13:43 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-18 02:13:43 (4119) [[32mINFO[0m] 
* 2023-07-18 02:13:43 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-18 02:13:43 (4089) [[32mINFO[0m] 
* 2023-07-18 02:14:11 (4102) [[32mINFO[0m] 
* 2023-07-18 02:14:11 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-18 02:14:12 (4119) [[32mINFO[0m] 
* 2023-07-18 02:14:12 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-18 02:14:12 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-18 02:14:35 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-18 02:14:37 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MBCir88Irm/ea_profile.json
* 2023-07-18 02:14:38 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/MBCir88Irm/ea_profile.json
* 2023-07-18 02:14:42 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-19 02:13:56 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-19 02:13:56 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-19 02:13:56 (4089) [[32mINFO[0m] 
* 2023-07-19 02:13:56 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-19 02:13:56 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-19 02:13:56 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-19 02:13:57 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-19 02:13:57 (4119) [[32mINFO[0m] 
* 2023-07-19 02:13:57 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-19 02:13:57 (4089) [[32mINFO[0m] 
* 2023-07-19 02:14:26 (4102) [[32mINFO[0m] 
* 2023-07-19 02:14:26 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-19 02:14:26 (4119) [[32mINFO[0m] 
* 2023-07-19 02:14:26 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-19 02:14:26 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-19 02:14:48 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-19 02:14:50 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JH2vjYvZ9_/ea_profile.json
* 2023-07-19 02:14:51 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/JH2vjYvZ9_/ea_profile.json
* 2023-07-19 02:14:54 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-20 02:16:08 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-20 02:16:08 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-20 02:16:08 (4089) [[32mINFO[0m] 
* 2023-07-20 02:16:08 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-20 02:16:08 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-20 02:16:08 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-20 02:16:08 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-20 02:16:08 (4119) [[32mINFO[0m] 
* 2023-07-20 02:16:08 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-20 02:16:08 (4089) [[32mINFO[0m] 
* 2023-07-20 02:16:39 (4102) [[32mINFO[0m] 
* 2023-07-20 02:16:39 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-20 02:16:39 (4119) [[32mINFO[0m] 
* 2023-07-20 02:16:39 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-20 02:16:39 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-20 02:17:03 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-20 02:17:03 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vwqSk4egeT/ea_profile.json
* 2023-07-20 02:17:04 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/vwqSk4egeT/ea_profile.json
* 2023-07-20 02:17:08 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-21 02:13:49 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-21 02:13:49 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-21 02:13:49 (4089) [[32mINFO[0m] 
* 2023-07-21 02:13:49 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-21 02:13:49 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-21 02:13:49 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-21 02:13:49 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-21 02:13:49 (4119) [[32mINFO[0m] 
* 2023-07-21 02:13:49 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-21 02:13:49 (4089) [[32mINFO[0m] 
* 2023-07-21 02:14:19 (4102) [[32mINFO[0m] 
* 2023-07-21 02:14:19 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-21 02:14:19 (4119) [[32mINFO[0m] 
* 2023-07-21 02:14:19 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-21 02:14:19 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-21 02:14:41 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-21 02:14:45 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/m3CZSEqmRW/ea_profile.json
* 2023-07-21 02:14:47 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/m3CZSEqmRW/ea_profile.json
* 2023-07-21 02:14:50 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-21 16:00:36 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-21 16:00:36 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-21 16:00:36 (4089) [[32mINFO[0m] 
* 2023-07-21 16:00:36 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-21 16:00:36 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-21 16:00:36 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-21 16:00:37 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-21 16:00:37 (4119) [[32mINFO[0m] 
* 2023-07-21 16:00:37 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-21 16:00:37 (4089) [[32mINFO[0m] 
* 2023-07-21 16:05:33 (4102) [[32mINFO[0m] 
* 2023-07-21 16:05:33 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-21 16:05:33 (4119) [[32mINFO[0m] 
* 2023-07-21 16:05:33 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-21 16:05:33 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-21 16:08:36 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-21 16:08:38 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iwUShTG6dp/ea_profile.json
* 2023-07-21 16:08:39 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/iwUShTG6dp/ea_profile.json
* 2023-07-21 16:08:42 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-22 02:14:16 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-22 02:14:16 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-22 02:14:16 (4089) [[32mINFO[0m] 
* 2023-07-22 02:14:16 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-22 02:14:16 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-22 02:14:16 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-22 02:14:17 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-22 02:14:17 (4119) [[32mINFO[0m] 
* 2023-07-22 02:14:17 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-22 02:14:17 (4089) [[32mINFO[0m] 
* 2023-07-22 02:14:45 (4102) [[32mINFO[0m] 
* 2023-07-22 02:14:45 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-22 02:14:45 (4119) [[32mINFO[0m] 
* 2023-07-22 02:14:45 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-22 02:14:45 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-22 02:15:11 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-22 02:15:11 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/r5avmEWcdR/ea_profile.json
* 2023-07-22 02:15:13 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/r5avmEWcdR/ea_profile.json
* 2023-07-22 02:15:16 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-23 02:14:18 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-23 02:14:18 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-23 02:14:18 (4089) [[32mINFO[0m] 
* 2023-07-23 02:14:19 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-23 02:14:19 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-23 02:14:19 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-23 02:14:19 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-23 02:14:19 (4119) [[32mINFO[0m] 
* 2023-07-23 02:14:19 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-23 02:14:19 (4089) [[32mINFO[0m] 
* 2023-07-23 02:14:49 (4102) [[32mINFO[0m] 
* 2023-07-23 02:14:49 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-23 02:14:49 (4119) [[32mINFO[0m] 
* 2023-07-23 02:14:49 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-23 02:14:49 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-23 02:15:13 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-23 02:15:13 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dgpzFHZSZT/ea_profile.json
* 2023-07-23 02:15:14 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/dgpzFHZSZT/ea_profile.json
* 2023-07-23 02:15:17 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-24 02:13:59 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-24 02:13:59 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-24 02:13:59 (4089) [[32mINFO[0m] 
* 2023-07-24 02:13:59 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-24 02:13:59 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-24 02:13:59 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-24 02:14:00 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-24 02:14:00 (4119) [[32mINFO[0m] 
* 2023-07-24 02:14:00 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-24 02:14:00 (4089) [[32mINFO[0m] 
* 2023-07-24 02:14:31 (4102) [[32mINFO[0m] 
* 2023-07-24 02:14:31 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-24 02:14:32 (4119) [[32mINFO[0m] 
* 2023-07-24 02:14:32 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-24 02:14:32 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-24 02:14:52 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-24 02:14:52 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZuBSO3A4Dm/ea_profile.json
* 2023-07-24 02:14:53 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/ZuBSO3A4Dm/ea_profile.json
* 2023-07-24 02:14:57 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-25 02:13:49 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-25 02:13:49 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-25 02:13:49 (4089) [[32mINFO[0m] 
* 2023-07-25 02:13:49 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-25 02:13:50 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-25 02:13:50 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-25 02:13:50 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-25 02:13:50 (4119) [[32mINFO[0m] 
* 2023-07-25 02:13:50 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-25 02:13:50 (4089) [[32mINFO[0m] 
* 2023-07-25 02:14:19 (4102) [[32mINFO[0m] 
* 2023-07-25 02:14:19 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-25 02:14:19 (4119) [[32mINFO[0m] 
* 2023-07-25 02:14:19 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-25 02:14:19 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-25 02:14:42 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-25 02:14:42 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_re84FKzS1/ea_profile.json
* 2023-07-25 02:14:44 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/_re84FKzS1/ea_profile.json
* 2023-07-25 02:14:47 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-26 02:14:10 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-26 02:14:10 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-26 02:14:10 (4089) [[32mINFO[0m] 
* 2023-07-26 02:14:10 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-26 02:14:10 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-26 02:14:10 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-26 02:14:10 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-26 02:14:10 (4119) [[32mINFO[0m] 
* 2023-07-26 02:14:10 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-26 02:14:10 (4089) [[32mINFO[0m] 
* 2023-07-26 02:17:31 (4102) [[32mINFO[0m] 
* 2023-07-26 02:17:31 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-26 02:17:31 (4119) [[32mINFO[0m] 
* 2023-07-26 02:17:31 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-26 02:17:31 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-26 02:17:58 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-26 02:18:00 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/O_258FaZZB/ea_profile.json
* 2023-07-26 02:18:01 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/O_258FaZZB/ea_profile.json
* 2023-07-26 02:18:04 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-27 02:13:49 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-27 02:13:49 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-27 02:13:49 (4089) [[32mINFO[0m] 
* 2023-07-27 02:13:50 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-27 02:13:50 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-27 02:13:50 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-27 02:13:50 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-27 02:13:51 (4119) [[32mINFO[0m] 
* 2023-07-27 02:13:51 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-27 02:13:51 (4089) [[32mINFO[0m] 
* 2023-07-27 02:14:23 (4102) [[32mINFO[0m] 
* 2023-07-27 02:14:23 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-27 02:14:23 (4119) [[32mINFO[0m] 
* 2023-07-27 02:14:23 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-27 02:14:23 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-27 02:14:43 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-27 02:14:45 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/83msn_x6hf/ea_profile.json
* 2023-07-27 02:14:47 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/83msn_x6hf/ea_profile.json
* 2023-07-27 02:14:50 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-28 02:15:56 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-28 02:15:56 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-28 02:15:56 (4089) [[32mINFO[0m] 
* 2023-07-28 02:15:56 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-28 02:15:56 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-28 02:15:56 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-28 02:15:56 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-28 02:15:56 (4119) [[32mINFO[0m] 
* 2023-07-28 02:15:56 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-28 02:15:56 (4089) [[32mINFO[0m] 
* 2023-07-28 02:16:31 (4102) [[32mINFO[0m] 
* 2023-07-28 02:16:31 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-28 02:16:31 (4119) [[32mINFO[0m] 
* 2023-07-28 02:16:31 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-28 02:16:31 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-28 02:16:54 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-28 02:16:54 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Rf8zk9AyQ_/ea_profile.json
* 2023-07-28 02:16:55 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/Rf8zk9AyQ_/ea_profile.json
* 2023-07-28 02:16:58 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-28 15:52:19 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-28 15:52:19 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-28 15:52:19 (4089) [[32mINFO[0m] 
* 2023-07-28 15:52:20 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-28 15:52:20 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-28 15:52:20 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-28 15:52:20 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-28 15:52:20 (4119) [[32mINFO[0m] 
* 2023-07-28 15:52:20 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-28 15:52:20 (4089) [[32mINFO[0m] 
* 2023-07-28 15:54:18 (4102) [[32mINFO[0m] 
* 2023-07-28 15:54:18 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-28 15:54:18 (4119) [[32mINFO[0m] 
* 2023-07-28 15:54:18 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-28 15:54:18 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-28 15:55:43 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-28 15:55:43 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GvSGC5K1iV/ea_profile.json
* 2023-07-28 15:55:45 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/GvSGC5K1iV/ea_profile.json
* 2023-07-28 15:55:54 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-29 02:14:51 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-29 02:14:51 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-29 02:14:51 (4089) [[32mINFO[0m] 
* 2023-07-29 02:14:51 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-29 02:14:51 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-29 02:14:51 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-29 02:14:51 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-29 02:14:51 (4119) [[32mINFO[0m] 
* 2023-07-29 02:14:51 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-29 02:14:51 (4089) [[32mINFO[0m] 
* 2023-07-29 02:15:20 (4102) [[32mINFO[0m] 
* 2023-07-29 02:15:20 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-29 02:15:21 (4119) [[32mINFO[0m] 
* 2023-07-29 02:15:21 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-29 02:15:21 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-29 02:15:42 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-29 02:15:46 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UDX5aQvXpt/ea_profile.json
* 2023-07-29 02:15:47 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/UDX5aQvXpt/ea_profile.json
* 2023-07-29 02:15:50 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-30 02:13:57 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-30 02:13:57 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-30 02:13:57 (4089) [[32mINFO[0m] 
* 2023-07-30 02:13:58 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-30 02:13:58 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-30 02:13:58 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-30 02:13:58 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-30 02:13:58 (4119) [[32mINFO[0m] 
* 2023-07-30 02:13:58 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-30 02:13:58 (4089) [[32mINFO[0m] 
* 2023-07-30 02:14:29 (4102) [[32mINFO[0m] 
* 2023-07-30 02:14:29 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-30 02:14:29 (4119) [[32mINFO[0m] 
* 2023-07-30 02:14:29 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-30 02:14:29 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-30 02:14:51 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-30 02:14:51 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cs9XwBnVuY/ea_profile.json
* 2023-07-30 02:14:53 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/cs9XwBnVuY/ea_profile.json
* 2023-07-30 02:14:56 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-31 02:13:36 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-07-31 02:13:36 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-07-31 02:13:36 (4089) [[32mINFO[0m] 
* 2023-07-31 02:13:36 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-31 02:13:37 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-07-31 02:13:37 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-07-31 02:13:37 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-07-31 02:13:37 (4119) [[32mINFO[0m] 
* 2023-07-31 02:13:37 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-07-31 02:13:37 (4089) [[32mINFO[0m] 
* 2023-07-31 02:14:06 (4102) [[32mINFO[0m] 
* 2023-07-31 02:14:06 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-31 02:14:06 (4119) [[32mINFO[0m] 
* 2023-07-31 02:14:06 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-31 02:14:06 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-31 02:14:28 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-31 02:14:30 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZNIWO5f2ad/ea_profile.json
* 2023-07-31 02:14:31 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/ZNIWO5f2ad/ea_profile.json
* 2023-07-31 02:14:34 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-01 02:17:49 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-01 02:17:49 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-01 02:17:49 (4089) [[32mINFO[0m] 
* 2023-08-01 02:17:50 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-01 02:17:50 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-01 02:17:50 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-01 02:17:50 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-01 02:17:50 (4119) [[32mINFO[0m] 
* 2023-08-01 02:17:50 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-01 02:17:50 (4089) [[32mINFO[0m] 
* 2023-08-01 02:18:29 (4102) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
* 2023-08-01 02:18:29 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-08-01 02:18:49 (4102) [[32mINFO[0m] 
* 2023-08-01 02:18:49 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-08-01 02:18:49 (4119) [[32mINFO[0m] 
* 2023-08-01 02:18:49 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-01 02:18:49 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-01 02:19:40 (1566) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-08-01 02:19:40 (1567) [[31mERROR[0m] Existing lock /var/run/yum.pid: another copy is running as pid 10841.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: repoquery
    Memory :  29 M RSS (379 MB VSZ)
    Started: Tue Aug  1 02:18:41 2023 - 00:09 ago
    State  : Running, pid: 10841
http://mirror.earthlink.iq/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on http://mirror.earthlink.iq/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-08-01 02:19:40 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-01 02:19:40 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-01 02:19:40 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PzuSgXHSHX/ea_profile.json
* 2023-08-01 02:19:42 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/PzuSgXHSHX/ea_profile.json
* 2023-08-01 02:19:45 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-02 02:13:48 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-02 02:13:48 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-02 02:13:48 (4089) [[32mINFO[0m] 
* 2023-08-02 02:13:49 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-02 02:13:49 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-02 02:13:49 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-02 02:13:49 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-02 02:13:49 (4119) [[32mINFO[0m] 
* 2023-08-02 02:13:49 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-02 02:13:49 (4089) [[32mINFO[0m] 
* 2023-08-02 02:14:19 (4102) [[32mINFO[0m] 
* 2023-08-02 02:14:19 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-08-02 02:14:19 (4119) [[32mINFO[0m] 
* 2023-08-02 02:14:19 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-02 02:14:19 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-02 02:14:39 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-02 02:14:40 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IBwAy07qpo/ea_profile.json
* 2023-08-02 02:14:41 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/IBwAy07qpo/ea_profile.json
* 2023-08-02 02:14:47 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-03 02:15:37 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-03 02:15:37 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-03 02:15:37 (4089) [[32mINFO[0m] 
* 2023-08-03 02:15:37 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-03 02:15:37 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-03 02:15:37 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-03 02:15:38 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-03 02:15:38 (4119) [[32mINFO[0m] 
* 2023-08-03 02:15:38 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-03 02:15:38 (4089) [[32mINFO[0m] 
* 2023-08-03 02:16:08 (4102) [[32mINFO[0m] 
* 2023-08-03 02:16:08 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-08-03 02:16:08 (4119) [[32mINFO[0m] 
* 2023-08-03 02:16:08 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-03 02:16:08 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-03 02:16:31 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-03 02:16:34 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/p3eOWCNO_E/ea_profile.json
* 2023-08-03 02:16:35 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/p3eOWCNO_E/ea_profile.json
* 2023-08-03 02:16:39 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-04 02:13:57 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-04 02:13:57 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-04 02:13:57 (4089) [[32mINFO[0m] 
* 2023-08-04 02:13:57 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-04 02:13:57 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-04 02:13:57 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-04 02:13:57 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-04 02:13:57 (4119) [[32mINFO[0m] 
* 2023-08-04 02:13:57 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-04 02:13:57 (4089) [[32mINFO[0m] 
* 2023-08-04 02:14:27 (4102) [[32mINFO[0m] 
* 2023-08-04 02:14:27 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-04 02:14:27 (4119) [[32mINFO[0m] 
* 2023-08-04 02:14:27 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-04 02:14:27 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-04 02:14:48 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-04 02:14:49 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cxZyjfdYAq/ea_profile.json
* 2023-08-04 02:14:51 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/cxZyjfdYAq/ea_profile.json
* 2023-08-04 02:14:54 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-04 15:49:23 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-04 15:49:23 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-04 15:49:23 (4089) [[32mINFO[0m] 
* 2023-08-04 15:49:23 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-04 15:49:23 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-04 15:49:23 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-04 15:49:24 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-04 15:49:24 (4119) [[32mINFO[0m] 
* 2023-08-04 15:49:24 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-04 15:49:24 (4089) [[32mINFO[0m] 
* 2023-08-04 15:49:52 (4102) [[32mINFO[0m] 
* 2023-08-04 15:49:52 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-04 15:49:53 (4119) [[32mINFO[0m] 
* 2023-08-04 15:49:53 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-04 15:49:53 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-04 15:50:14 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-04 15:50:16 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gqdqNjbKIM/ea_profile.json
* 2023-08-04 15:50:18 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/gqdqNjbKIM/ea_profile.json
* 2023-08-04 15:50:21 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-05 02:14:08 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-05 02:14:08 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-05 02:14:08 (4089) [[32mINFO[0m] 
* 2023-08-05 02:14:08 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-05 02:14:08 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-05 02:14:08 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-05 02:14:08 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-05 02:14:08 (4119) [[32mINFO[0m] 
* 2023-08-05 02:14:08 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-05 02:14:08 (4089) [[32mINFO[0m] 
* 2023-08-05 02:14:38 (4102) [[32mINFO[0m] 
* 2023-08-05 02:14:38 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-05 02:14:38 (4119) [[32mINFO[0m] 
* 2023-08-05 02:14:38 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-05 02:14:38 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-05 02:15:00 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-05 02:15:00 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pkmZtZO8vI/ea_profile.json
* 2023-08-05 02:15:01 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/pkmZtZO8vI/ea_profile.json
* 2023-08-05 02:15:04 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-06 02:14:07 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-06 02:14:07 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-06 02:14:07 (4089) [[32mINFO[0m] 
* 2023-08-06 02:14:07 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-06 02:14:07 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-06 02:14:07 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-06 02:14:07 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-06 02:14:07 (4119) [[32mINFO[0m] 
* 2023-08-06 02:14:07 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-06 02:14:07 (4089) [[32mINFO[0m] 
* 2023-08-06 02:14:37 (4102) [[32mINFO[0m] 
* 2023-08-06 02:14:37 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-06 02:14:37 (4119) [[32mINFO[0m] 
* 2023-08-06 02:14:37 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-06 02:14:37 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-06 02:14:57 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-06 02:14:59 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zMZoIGto6U/ea_profile.json
* 2023-08-06 02:15:01 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/zMZoIGto6U/ea_profile.json
* 2023-08-06 02:15:04 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-07 02:14:01 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-07 02:14:01 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-07 02:14:01 (4089) [[32mINFO[0m] 
* 2023-08-07 02:14:01 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-07 02:14:01 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-07 02:14:01 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-07 02:14:01 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-07 02:14:01 (4119) [[32mINFO[0m] 
* 2023-08-07 02:14:01 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-07 02:14:01 (4089) [[32mINFO[0m] 
* 2023-08-07 02:14:28 (4102) [[32mINFO[0m] 
* 2023-08-07 02:14:28 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-07 02:14:29 (4119) [[32mINFO[0m] 
* 2023-08-07 02:14:29 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-07 02:14:29 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-07 02:14:50 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-07 02:14:50 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/chmLJhbiNN/ea_profile.json
* 2023-08-07 02:14:51 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/chmLJhbiNN/ea_profile.json
* 2023-08-07 02:14:57 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-08 02:14:05 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-08 02:14:05 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-08 02:14:05 (4089) [[32mINFO[0m] 
* 2023-08-08 02:14:05 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-08 02:14:06 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-08 02:14:06 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-08 02:14:06 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-08 02:14:06 (4119) [[32mINFO[0m] 
* 2023-08-08 02:14:06 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-08 02:14:06 (4089) [[32mINFO[0m] 
* 2023-08-08 02:14:35 (4102) [[32mINFO[0m] 
* 2023-08-08 02:14:35 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-08 02:14:35 (4119) [[32mINFO[0m] 
* 2023-08-08 02:14:35 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-08 02:14:35 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-08 02:15:01 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-08 02:15:01 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6btk2f1gl7/ea_profile.json
* 2023-08-08 02:15:03 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/6btk2f1gl7/ea_profile.json
* 2023-08-08 02:15:06 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-09 02:14:13 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-09 02:14:13 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-09 02:14:13 (4089) [[32mINFO[0m] 
* 2023-08-09 02:14:13 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-09 02:14:13 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-09 02:14:13 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-09 02:14:13 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-09 02:14:13 (4119) [[32mINFO[0m] 
* 2023-08-09 02:14:13 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-09 02:14:13 (4089) [[32mINFO[0m] 
* 2023-08-09 02:15:14 (4102) [[32mINFO[0m] 
* 2023-08-09 02:15:14 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-09 02:15:14 (4119) [[32mINFO[0m] 
* 2023-08-09 02:15:14 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-09 02:15:14 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-09 02:15:37 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-09 02:15:37 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RvXZIz1AFZ/ea_profile.json
* 2023-08-09 02:15:38 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/RvXZIz1AFZ/ea_profile.json
* 2023-08-09 02:15:41 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-10 02:16:37 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-10 02:16:37 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-10 02:16:37 (4089) [[32mINFO[0m] 
* 2023-08-10 02:16:37 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-10 02:16:37 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-10 02:16:37 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-10 02:16:37 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-10 02:16:38 (4119) [[32mINFO[0m] 
* 2023-08-10 02:16:38 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-10 02:16:38 (4089) [[32mINFO[0m] 
* 2023-08-10 02:17:06 (4102) [[32mINFO[0m] 
* 2023-08-10 02:17:06 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-10 02:17:06 (4119) [[32mINFO[0m] 
* 2023-08-10 02:17:06 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-10 02:17:06 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-10 02:17:28 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-10 02:17:28 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DNZFlz9BxC/ea_profile.json
* 2023-08-10 02:17:29 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/DNZFlz9BxC/ea_profile.json
* 2023-08-10 02:17:36 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-11 02:16:37 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-11 02:16:37 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-11 02:16:37 (4089) [[32mINFO[0m] 
* 2023-08-11 02:16:37 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-11 02:16:37 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-11 02:16:37 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-11 02:16:37 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-11 02:16:37 (4119) [[32mINFO[0m] 
* 2023-08-11 02:16:37 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-11 02:16:37 (4089) [[32mINFO[0m] 
* 2023-08-11 02:17:21 (4102) [[32mINFO[0m] http://istanbul.centos-mirror.guzel.net.tr/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on http://istanbul.centos-mirror.guzel.net.tr/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-08-11 02:17:21 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-08-11 02:17:37 (4102) [[32mINFO[0m] 
* 2023-08-11 02:17:37 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-11 02:17:37 (4119) [[32mINFO[0m] 
* 2023-08-11 02:17:37 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-11 02:17:37 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-11 02:17:59 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-11 02:18:01 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HcPSjfGsIH/ea_profile.json
* 2023-08-11 02:18:02 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/HcPSjfGsIH/ea_profile.json
* 2023-08-11 02:18:05 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-11 15:49:09 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-11 15:49:09 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-11 15:49:09 (4089) [[32mINFO[0m] 
* 2023-08-11 15:49:09 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-11 15:49:09 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-11 15:49:09 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-11 15:49:09 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-11 15:49:09 (4119) [[32mINFO[0m] 
* 2023-08-11 15:49:09 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-11 15:49:09 (4089) [[32mINFO[0m] 
* 2023-08-11 15:49:36 (4102) [[32mINFO[0m] 
* 2023-08-11 15:49:36 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-11 15:49:37 (4119) [[32mINFO[0m] 
* 2023-08-11 15:49:37 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-11 15:49:37 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-11 15:50:20 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-11 15:50:20 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wRkviqP5Yc/ea_profile.json
* 2023-08-11 15:50:21 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/wRkviqP5Yc/ea_profile.json
* 2023-08-11 15:50:24 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-12 02:14:17 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-12 02:14:17 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-12 02:14:17 (4089) [[32mINFO[0m] 
* 2023-08-12 02:14:17 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-12 02:14:17 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-12 02:14:17 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-12 02:14:17 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-12 02:14:17 (4119) [[32mINFO[0m] 
* 2023-08-12 02:14:17 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-12 02:14:17 (4089) [[32mINFO[0m] 
* 2023-08-12 02:14:51 (4102) [[32mINFO[0m] 
* 2023-08-12 02:14:51 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-12 02:14:51 (4119) [[32mINFO[0m] 
* 2023-08-12 02:14:51 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-12 02:14:51 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-12 02:15:13 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-12 02:15:16 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6EOTDyFcSC/ea_profile.json
* 2023-08-12 02:15:18 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/6EOTDyFcSC/ea_profile.json
* 2023-08-12 02:15:21 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-13 02:21:14 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-13 02:21:14 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-13 02:21:14 (4089) [[32mINFO[0m] 
* 2023-08-13 02:21:14 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-13 02:21:14 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-13 02:21:14 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-13 02:21:14 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-13 02:21:14 (4119) [[32mINFO[0m] 
* 2023-08-13 02:21:14 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-13 02:21:14 (4089) [[32mINFO[0m] 
* 2023-08-13 02:21:45 (4102) [[32mINFO[0m] 
* 2023-08-13 02:21:45 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-13 02:21:45 (4119) [[32mINFO[0m] 
* 2023-08-13 02:21:45 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-13 02:21:45 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-13 02:22:05 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-13 02:22:05 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SFI4ZnDq8_/ea_profile.json
* 2023-08-13 02:22:06 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/SFI4ZnDq8_/ea_profile.json
* 2023-08-13 02:22:12 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-14 02:14:23 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-14 02:14:23 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-14 02:14:23 (4089) [[32mINFO[0m] 
* 2023-08-14 02:14:23 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-14 02:14:23 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-14 02:14:23 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-14 02:14:24 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-14 02:14:24 (4119) [[32mINFO[0m] 
* 2023-08-14 02:14:24 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-14 02:14:24 (4089) [[32mINFO[0m] 
* 2023-08-14 02:14:53 (4102) [[32mINFO[0m] 
* 2023-08-14 02:14:53 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-14 02:14:53 (4119) [[32mINFO[0m] 
* 2023-08-14 02:14:53 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-14 02:14:53 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-14 02:15:14 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-14 02:15:14 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/I3ffFhsnWV/ea_profile.json
* 2023-08-14 02:15:15 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/I3ffFhsnWV/ea_profile.json
* 2023-08-14 02:15:22 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-15 02:14:15 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-15 02:14:15 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-15 02:14:15 (4089) [[32mINFO[0m] 
* 2023-08-15 02:14:15 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-15 02:14:15 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-15 02:14:15 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-15 02:14:15 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-15 02:14:15 (4119) [[32mINFO[0m] 
* 2023-08-15 02:14:15 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-15 02:14:15 (4089) [[32mINFO[0m] 
* 2023-08-15 02:14:51 (4102) [[32mINFO[0m] 
* 2023-08-15 02:14:51 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-15 02:14:51 (4119) [[32mINFO[0m] 
* 2023-08-15 02:14:51 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-15 02:14:51 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-15 02:15:11 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-15 02:15:15 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rgu8FdUraG/ea_profile.json
* 2023-08-15 02:15:16 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/rgu8FdUraG/ea_profile.json
* 2023-08-15 02:15:19 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-16 02:13:38 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-16 02:13:38 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-16 02:13:38 (4089) [[32mINFO[0m] 
* 2023-08-16 02:13:38 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-16 02:13:38 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-16 02:13:38 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-16 02:13:39 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-16 02:13:39 (4119) [[32mINFO[0m] 
* 2023-08-16 02:13:39 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-16 02:13:39 (4089) [[32mINFO[0m] 
* 2023-08-16 02:14:07 (4102) [[32mINFO[0m] 
* 2023-08-16 02:14:07 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-16 02:14:07 (4119) [[32mINFO[0m] 
* 2023-08-16 02:14:07 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-16 02:14:07 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-16 02:14:27 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-16 02:14:32 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MRgDRo1ZPO/ea_profile.json
* 2023-08-16 02:14:33 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/MRgDRo1ZPO/ea_profile.json
* 2023-08-16 02:14:36 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-17 02:16:22 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-08-17 02:16:23 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-17 02:16:23 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-17 02:16:23 (4089) [[32mINFO[0m] 
* 2023-08-17 02:16:23 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-17 02:16:24 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-17 02:16:24 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-17 02:16:24 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-17 02:16:24 (4119) [[32mINFO[0m] 
* 2023-08-17 02:16:24 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-17 02:16:24 (4089) [[32mINFO[0m] 
* 2023-08-17 02:17:02 (4102) [[32mINFO[0m] 
* 2023-08-17 02:17:02 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-17 02:17:02 (4119) [[32mINFO[0m] 
* 2023-08-17 02:17:02 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-17 02:17:02 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-17 02:17:23 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-17 02:17:25 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pUsNcjQmQk/ea_profile.json
* 2023-08-17 02:17:27 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/pUsNcjQmQk/ea_profile.json
* 2023-08-17 02:17:30 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-18 02:14:17 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-18 02:14:17 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-18 02:14:17 (4089) [[32mINFO[0m] 
* 2023-08-18 02:14:18 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-18 02:14:18 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-18 02:14:18 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-18 02:14:18 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-18 02:14:18 (4119) [[32mINFO[0m] 
* 2023-08-18 02:14:18 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-18 02:14:18 (4089) [[32mINFO[0m] 
* 2023-08-18 02:15:01 (4102) [[32mINFO[0m] 
* 2023-08-18 02:15:01 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-18 02:15:01 (4119) [[32mINFO[0m] 
* 2023-08-18 02:15:01 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-18 02:15:01 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-18 02:15:27 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-18 02:15:27 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fz_of9IXnn/ea_profile.json
* 2023-08-18 02:15:29 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/fz_of9IXnn/ea_profile.json
* 2023-08-18 02:15:32 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-18 15:49:35 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-18 15:49:35 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-18 15:49:35 (4089) [[32mINFO[0m] 
* 2023-08-18 15:49:35 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-18 15:49:36 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-18 15:49:36 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-18 15:49:36 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-18 15:49:36 (4119) [[32mINFO[0m] 
* 2023-08-18 15:49:36 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-18 15:49:36 (4089) [[32mINFO[0m] 
* 2023-08-18 15:50:32 (4102) [[32mINFO[0m] 
* 2023-08-18 15:50:32 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-18 15:50:32 (4119) [[32mINFO[0m] 
* 2023-08-18 15:50:32 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-18 15:50:32 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-18 15:51:13 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-18 15:51:13 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YyjcsV1JZE/ea_profile.json
* 2023-08-18 15:51:14 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/YyjcsV1JZE/ea_profile.json
* 2023-08-18 15:51:18 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-19 02:14:28 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-19 02:14:28 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-19 02:14:28 (4089) [[32mINFO[0m] 
* 2023-08-19 02:14:28 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-19 02:14:28 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-19 02:14:28 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-19 02:14:29 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-19 02:14:29 (4119) [[32mINFO[0m] 
* 2023-08-19 02:14:29 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-19 02:14:29 (4089) [[32mINFO[0m] 
* 2023-08-19 02:14:56 (4102) [[32mINFO[0m] 
* 2023-08-19 02:14:56 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-19 02:14:56 (4119) [[32mINFO[0m] 
* 2023-08-19 02:14:56 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-19 02:14:56 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-19 02:15:17 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-19 02:15:17 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VCNsDYMB8a/ea_profile.json
* 2023-08-19 02:15:18 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/VCNsDYMB8a/ea_profile.json
* 2023-08-19 02:15:24 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-20 02:14:25 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-20 02:14:25 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-20 02:14:25 (4089) [[32mINFO[0m] 
* 2023-08-20 02:14:25 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-20 02:14:25 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-20 02:14:25 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-20 02:14:25 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-20 02:14:25 (4119) [[32mINFO[0m] 
* 2023-08-20 02:14:25 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-20 02:14:25 (4089) [[32mINFO[0m] 
* 2023-08-20 02:14:57 (4102) [[32mINFO[0m] 
* 2023-08-20 02:14:57 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-20 02:14:57 (4119) [[32mINFO[0m] 
* 2023-08-20 02:14:57 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-20 02:14:57 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-20 02:15:16 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-20 02:15:17 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lP4CIT4YZw/ea_profile.json
* 2023-08-20 02:15:19 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/lP4CIT4YZw/ea_profile.json
* 2023-08-20 02:15:23 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-21 02:17:06 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-21 02:17:06 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-21 02:17:06 (4089) [[32mINFO[0m] 
* 2023-08-21 02:17:07 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-21 02:17:07 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-21 02:17:07 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-21 02:17:07 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-21 02:17:07 (4119) [[32mINFO[0m] 
* 2023-08-21 02:17:07 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-21 02:17:07 (4089) [[32mINFO[0m] 
* 2023-08-21 02:17:37 (4102) [[32mINFO[0m] 
* 2023-08-21 02:17:37 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-21 02:17:37 (4119) [[32mINFO[0m] 
* 2023-08-21 02:17:37 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-21 02:17:37 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-21 02:18:06 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-21 02:18:06 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RRXNkeQhIZ/ea_profile.json
* 2023-08-21 02:18:08 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/RRXNkeQhIZ/ea_profile.json
* 2023-08-21 02:18:11 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-22 02:16:00 (153) [[33mWARN[0m] *** 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 194.5.188.42.
Verify whether that IP address is licensed using the following site:

https://verify.cpanel.net/


* 2023-08-22 02:16:01 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-22 02:16:01 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-22 02:16:01 (4089) [[32mINFO[0m] 
* 2023-08-22 02:16:01 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-22 02:16:01 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-22 02:16:01 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-22 02:16:01 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-22 02:16:01 (4119) [[32mINFO[0m] 
* 2023-08-22 02:16:01 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-22 02:16:01 (4089) [[32mINFO[0m] 
* 2023-08-22 02:16:38 (4102) [[32mINFO[0m] 
* 2023-08-22 02:16:38 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-22 02:16:38 (4119) [[32mINFO[0m] 
* 2023-08-22 02:16:38 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-22 02:16:38 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-22 02:16:58 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-22 02:16:59 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZFeA_FWwgS/ea_profile.json
* 2023-08-22 02:17:01 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/ZFeA_FWwgS/ea_profile.json
* 2023-08-22 02:17:12 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-23 02:13:23 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-23 02:13:23 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-23 02:13:23 (4089) [[32mINFO[0m] 
* 2023-08-23 02:13:24 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-23 02:13:24 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-23 02:13:24 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-23 02:13:24 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-23 02:13:24 (4119) [[32mINFO[0m] 
* 2023-08-23 02:13:24 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-23 02:13:24 (4089) [[32mINFO[0m] 
* 2023-08-23 02:13:56 (4102) [[32mINFO[0m] 
* 2023-08-23 02:13:56 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-23 02:13:56 (4119) [[32mINFO[0m] 
* 2023-08-23 02:13:56 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-23 02:13:56 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-23 02:14:20 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-23 02:14:21 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ALl_6rVMhZ/ea_profile.json
* 2023-08-23 02:14:22 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/ALl_6rVMhZ/ea_profile.json
* 2023-08-23 02:14:26 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-24 02:13:41 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-24 02:13:41 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-24 02:13:41 (4089) [[32mINFO[0m] 
* 2023-08-24 02:13:41 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-24 02:13:41 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-24 02:13:41 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-24 02:13:41 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-24 02:13:41 (4119) [[32mINFO[0m] 
* 2023-08-24 02:13:41 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-24 02:13:41 (4089) [[32mINFO[0m] 
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m] 12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m] 
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m] 
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m] 
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m] 
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m] 
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m] 
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m] 
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]         or
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m] 
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]         compromise:
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m] 
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m] 
* 2023-08-24 02:14:12 (4102) [[32mINFO[0m] Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2023-08-24 02:14:12 (4119) [[32mINFO[0m] 
* 2023-08-24 02:14:12 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-24 02:14:12 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-08-24 02:14:12 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-08-24 02:14:12 (4089) [[32mINFO[0m] 
* 2023-08-24 02:14:13 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-08-24 02:14:14 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-08-24 02:14:14 (4119) [[32mINFO[0m] 
* 2023-08-24 02:14:50 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-24 02:14:50 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/a3BcSj1Rii/ea_profile.json
* 2023-08-24 02:14:52 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/a3BcSj1Rii/ea_profile.json
* 2023-08-24 02:14:55 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-08-25 02:13:30 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-25 02:13:30 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-25 02:13:30 (4089) [[32mINFO[0m] 
* 2023-08-25 02:13:30 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-25 02:13:30 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-25 02:13:30 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-25 02:13:31 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-25 02:13:31 (4119) [[32mINFO[0m] 
* 2023-08-25 02:13:31 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-25 02:13:31 (4089) [[32mINFO[0m] 
* 2023-08-25 02:14:00 (4102) [[32mINFO[0m] 
* 2023-08-25 02:14:00 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-25 02:14:00 (4119) [[32mINFO[0m] 
* 2023-08-25 02:14:00 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-25 02:14:00 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-25 02:14:22 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-25 02:14:25 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ehjr9xA5k6/ea_profile.json
* 2023-08-25 02:14:26 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/ehjr9xA5k6/ea_profile.json
* 2023-08-25 02:14:30 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-25 15:49:06 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-25 15:49:06 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-25 15:49:06 (4089) [[32mINFO[0m] 
* 2023-08-25 15:49:07 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-25 15:49:07 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-25 15:49:07 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-25 15:49:07 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-25 15:49:07 (4119) [[32mINFO[0m] 
* 2023-08-25 15:49:07 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-25 15:49:07 (4089) [[32mINFO[0m] 
* 2023-08-25 15:49:55 (4102) [[32mINFO[0m] 
* 2023-08-25 15:49:55 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-25 15:49:56 (4119) [[32mINFO[0m] 
* 2023-08-25 15:49:56 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-25 15:49:56 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-25 15:50:14 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-25 15:50:14 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QvgEjVmom7/ea_profile.json
* 2023-08-25 15:50:16 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/QvgEjVmom7/ea_profile.json
* 2023-08-25 15:50:23 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-26 02:16:12 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-26 02:16:12 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-26 02:16:12 (4089) [[32mINFO[0m] 
* 2023-08-26 02:16:12 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-26 02:16:12 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-26 02:16:12 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-26 02:16:13 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-26 02:16:13 (4119) [[32mINFO[0m] 
* 2023-08-26 02:16:13 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-26 02:16:13 (4089) [[32mINFO[0m] 
* 2023-08-26 02:16:45 (4102) [[32mINFO[0m] 
* 2023-08-26 02:16:45 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-26 02:16:46 (4119) [[32mINFO[0m] 
* 2023-08-26 02:16:46 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-26 02:16:46 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-26 02:17:06 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-26 02:17:07 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sFi1HCcsWF/ea_profile.json
* 2023-08-26 02:17:09 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/sFi1HCcsWF/ea_profile.json
* 2023-08-26 02:17:12 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-27 02:14:35 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-27 02:14:35 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-27 02:14:35 (4089) [[32mINFO[0m] 
* 2023-08-27 02:14:35 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-27 02:14:35 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-27 02:14:35 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-27 02:14:36 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-27 02:14:36 (4119) [[32mINFO[0m] 
* 2023-08-27 02:14:36 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-27 02:14:36 (4089) [[32mINFO[0m] 
* 2023-08-27 02:15:05 (4102) [[32mINFO[0m] 
* 2023-08-27 02:15:05 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-27 02:15:05 (4119) [[32mINFO[0m] 
* 2023-08-27 02:15:05 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-27 02:15:05 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-27 02:15:25 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-27 02:15:27 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rG5kbkv3v6/ea_profile.json
* 2023-08-27 02:15:29 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/rG5kbkv3v6/ea_profile.json
* 2023-08-27 02:15:33 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-28 02:13:39 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-28 02:13:39 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-28 02:13:39 (4089) [[32mINFO[0m] 
* 2023-08-28 02:13:39 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-28 02:13:40 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-28 02:13:40 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-28 02:13:40 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-28 02:13:40 (4119) [[32mINFO[0m] 
* 2023-08-28 02:13:40 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-28 02:13:40 (4089) [[32mINFO[0m] 
* 2023-08-28 02:14:26 (4102) [[32mINFO[0m] 
* 2023-08-28 02:14:26 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-28 02:14:26 (4119) [[32mINFO[0m] 
* 2023-08-28 02:14:26 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-28 02:14:26 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-28 02:14:49 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-28 02:14:52 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zKqW1ef0hz/ea_profile.json
* 2023-08-28 02:14:54 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/zKqW1ef0hz/ea_profile.json
* 2023-08-28 02:14:58 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-29 02:13:59 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-29 02:13:59 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-29 02:13:59 (4089) [[32mINFO[0m] 
* 2023-08-29 02:13:59 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-29 02:13:59 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-29 02:13:59 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-29 02:13:59 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-29 02:13:59 (4119) [[32mINFO[0m] 
* 2023-08-29 02:13:59 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-29 02:13:59 (4089) [[32mINFO[0m] 
* 2023-08-29 02:14:29 (4102) [[32mINFO[0m] 
* 2023-08-29 02:14:29 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-29 02:14:29 (4119) [[32mINFO[0m] 
* 2023-08-29 02:14:29 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-29 02:14:29 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-29 02:14:51 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-29 02:14:53 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JMGnOEQJr1/ea_profile.json
* 2023-08-29 02:14:54 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/JMGnOEQJr1/ea_profile.json
* 2023-08-29 02:14:58 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-30 02:13:33 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-30 02:13:33 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-30 02:13:33 (4089) [[32mINFO[0m] 
* 2023-08-30 02:13:33 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-30 02:13:33 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-30 02:13:33 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-30 02:13:33 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-30 02:13:33 (4119) [[32mINFO[0m] 
* 2023-08-30 02:13:33 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-30 02:13:33 (4089) [[32mINFO[0m] 
* 2023-08-30 02:14:02 (4102) [[32mINFO[0m] 
* 2023-08-30 02:14:02 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-30 02:14:02 (4119) [[32mINFO[0m] 
* 2023-08-30 02:14:02 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-30 02:14:02 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-30 02:14:22 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-30 02:14:26 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/J8FaI34x2y/ea_profile.json
* 2023-08-30 02:14:27 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/J8FaI34x2y/ea_profile.json
* 2023-08-30 02:14:31 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-31 02:13:31 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-08-31 02:13:31 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-08-31 02:13:31 (4089) [[32mINFO[0m] 
* 2023-08-31 02:13:31 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-31 02:13:32 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-08-31 02:13:32 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-08-31 02:13:32 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-08-31 02:13:32 (4119) [[32mINFO[0m] 
* 2023-08-31 02:13:32 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-08-31 02:13:32 (4089) [[32mINFO[0m] 
* 2023-08-31 02:14:00 (4102) [[32mINFO[0m] 
* 2023-08-31 02:14:00 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-31 02:14:00 (4119) [[32mINFO[0m] 
* 2023-08-31 02:14:00 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-31 02:14:00 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-31 02:14:21 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-31 02:14:23 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/f8W0o5mOMB/ea_profile.json
* 2023-08-31 02:14:27 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/f8W0o5mOMB/ea_profile.json
* 2023-08-31 02:14:30 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-01 02:13:42 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-01 02:13:42 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-01 02:13:42 (4089) [[32mINFO[0m] 
* 2023-09-01 02:13:42 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-01 02:13:42 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-01 02:13:42 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-09-01 02:13:43 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-01 02:13:43 (4119) [[32mINFO[0m] 
* 2023-09-01 02:13:43 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-01 02:13:43 (4089) [[32mINFO[0m] 
* 2023-09-01 02:14:10 (4102) [[32mINFO[0m] 
* 2023-09-01 02:14:10 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-01 02:14:11 (4119) [[32mINFO[0m] 
* 2023-09-01 02:14:11 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-01 02:14:11 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-01 02:14:31 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-01 02:14:31 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/n_FHUPJSWe/ea_profile.json
* 2023-09-01 02:14:33 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/n_FHUPJSWe/ea_profile.json
* 2023-09-01 02:14:39 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-01 15:50:54 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-01 15:50:54 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-01 15:50:54 (4089) [[32mINFO[0m] 
* 2023-09-01 15:50:54 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-01 15:50:54 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-01 15:50:54 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-09-01 15:50:55 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-01 15:50:55 (4119) [[32mINFO[0m] 
* 2023-09-01 15:50:55 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-01 15:50:55 (4089) [[32mINFO[0m] 
* 2023-09-01 15:51:45 (4102) [[32mINFO[0m] 
* 2023-09-01 15:51:45 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-01 15:51:45 (4119) [[32mINFO[0m] 
* 2023-09-01 15:51:45 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-01 15:51:45 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-01 15:52:29 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-01 15:52:29 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pDPKjsnqmw/ea_profile.json
* 2023-09-01 15:52:31 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/pDPKjsnqmw/ea_profile.json
* 2023-09-01 15:52:34 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-02 02:14:13 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-02 02:14:13 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-02 02:14:13 (4089) [[32mINFO[0m] 
* 2023-09-02 02:14:13 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-02 02:14:13 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-02 02:14:13 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-09-02 02:14:13 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-02 02:14:13 (4119) [[32mINFO[0m] 
* 2023-09-02 02:14:13 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-02 02:14:13 (4089) [[32mINFO[0m] 
* 2023-09-02 02:14:44 (4102) [[32mINFO[0m] 
* 2023-09-02 02:14:44 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-02 02:14:44 (4119) [[32mINFO[0m] 
* 2023-09-02 02:14:44 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-02 02:14:44 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-02 02:15:05 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-02 02:15:06 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_0I1h2Xcuo/ea_profile.json
* 2023-09-02 02:15:08 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/_0I1h2Xcuo/ea_profile.json
* 2023-09-02 02:15:11 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-03 02:14:10 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-03 02:14:10 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-03 02:14:10 (4089) [[32mINFO[0m] 
* 2023-09-03 02:14:11 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-03 02:14:11 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-03 02:14:11 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-09-03 02:14:11 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-03 02:14:11 (4119) [[32mINFO[0m] 
* 2023-09-03 02:14:11 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-03 02:14:11 (4089) [[32mINFO[0m] 
* 2023-09-03 02:14:40 (4102) [[32mINFO[0m] 
* 2023-09-03 02:14:40 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-03 02:14:41 (4119) [[32mINFO[0m] 
* 2023-09-03 02:14:41 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-03 02:14:41 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-03 02:15:02 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-03 02:15:05 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/d4hR4Dq18Z/ea_profile.json
* 2023-09-03 02:15:06 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/d4hR4Dq18Z/ea_profile.json
* 2023-09-03 02:15:10 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-04 02:13:24 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-04 02:13:24 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-04 02:13:24 (4089) [[32mINFO[0m] 
* 2023-09-04 02:13:25 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-04 02:13:25 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-04 02:13:25 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-09-04 02:13:25 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-04 02:13:25 (4119) [[32mINFO[0m] 
* 2023-09-04 02:13:25 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-04 02:13:25 (4089) [[32mINFO[0m] 
* 2023-09-04 02:13:55 (4102) [[32mINFO[0m] 
* 2023-09-04 02:13:55 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-04 02:13:55 (4119) [[32mINFO[0m] 
* 2023-09-04 02:13:55 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-04 02:13:55 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-04 02:14:15 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-04 02:14:15 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TvDSL0shE5/ea_profile.json
* 2023-09-04 02:14:16 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/TvDSL0shE5/ea_profile.json
* 2023-09-04 02:14:23 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-05 02:13:21 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-05 02:13:21 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-05 02:13:21 (4089) [[32mINFO[0m] 
* 2023-09-05 02:13:22 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-05 02:13:22 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-05 02:13:22 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-09-05 02:13:22 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-05 02:13:22 (4119) [[32mINFO[0m] 
* 2023-09-05 02:13:22 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-05 02:13:22 (4089) [[32mINFO[0m] 
* 2023-09-05 02:13:50 (4102) [[32mINFO[0m] 
* 2023-09-05 02:13:50 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-05 02:13:50 (4119) [[32mINFO[0m] 
* 2023-09-05 02:13:50 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-05 02:13:50 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-05 02:14:12 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-05 02:14:12 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/z5KzdQMz23/ea_profile.json
* 2023-09-05 02:14:13 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/z5KzdQMz23/ea_profile.json
* 2023-09-05 02:14:19 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-06 02:14:07 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-06 02:14:07 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-06 02:14:07 (4089) [[32mINFO[0m] 
* 2023-09-06 02:14:08 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-06 02:14:08 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-06 02:14:08 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-09-06 02:14:08 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-06 02:14:08 (4119) [[32mINFO[0m] 
* 2023-09-06 02:14:08 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-06 02:14:08 (4089) [[32mINFO[0m] 
* 2023-09-06 02:14:25 (4102) [[32mINFO[0m] http://centos.vargonen.com/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
* 2023-09-06 02:14:25 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-09-06 02:14:41 (4102) [[32mINFO[0m] 
* 2023-09-06 02:14:41 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-06 02:14:41 (4119) [[32mINFO[0m] 
* 2023-09-06 02:14:41 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-06 02:14:41 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-06 02:15:38 (1566) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-09-06 02:15:38 (1567) [[31mERROR[0m] http://centos.vargonen.com/centos/7.9.2009/updates/x86_64/repodata/0808ffa27434f694d97ba4cc05d65e2921dac75ba399ac956ddbec97ee1c36a1-other.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
Trying other mirror.
http://centos.vargonen.com/centos/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
Trying other mirror.
* 2023-09-06 02:15:38 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-06 02:15:38 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-06 02:15:38 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Tmtodh4bbP/ea_profile.json
* 2023-09-06 02:15:40 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/Tmtodh4bbP/ea_profile.json
* 2023-09-06 02:15:43 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-07 02:13:23 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-07 02:13:23 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-07 02:13:23 (4089) [[32mINFO[0m] 
* 2023-09-07 02:13:23 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-07 02:13:24 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-07 02:13:24 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-09-07 02:13:24 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-07 02:13:24 (4119) [[32mINFO[0m] 
* 2023-09-07 02:13:24 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-07 02:13:24 (4089) [[32mINFO[0m] 
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m] 12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m] 
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m] 
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m] 
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m] 
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m] 
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m] 
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m] 
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]         or
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m] 
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]         compromise:
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m] 
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m] 
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m] Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2023-09-07 02:13:55 (4119) [[32mINFO[0m] 
* 2023-09-07 02:13:55 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-07 02:13:55 (1721) [[32mINFO[0m] Checking /scripts/sysup
* 2023-09-07 02:13:55 (4088) [[32mINFO[0m] Running: /scripts/sysup
* 2023-09-07 02:13:55 (4089) [[32mINFO[0m] 
* 2023-09-07 02:13:55 (4102) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-09-07 02:13:57 (4102) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-09-07 02:13:57 (4119) [[32mINFO[0m] 
* 2023-09-07 02:14:37 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-07 02:14:37 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RAwM_9ygeA/ea_profile.json
* 2023-09-07 02:14:38 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/RAwM_9ygeA/ea_profile.json
* 2023-09-07 02:14:42 (269) [[32mINFO[0m] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-09-08 02:13:36 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-08 02:13:36 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-08 02:13:36 (4089) [[32mINFO[0m] 
* 2023-09-08 02:13:37 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-08 02:13:37 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-08 02:13:37 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-09-08 02:13:37 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-08 02:13:37 (4119) [[32mINFO[0m] 
* 2023-09-08 02:13:37 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-08 02:13:37 (4089) [[32mINFO[0m] 
* 2023-09-08 02:13:51 (4102) [[32mINFO[0m] https://mirror.hostart.az/fedora-epel/7/x86_64/repodata/784bc432f81a33845003c8946b146e08dbd0cbfef487c9728758bed3f83dd84e-primary.sqlite.bz2: [Errno 14] curl#60 - "Peer's Certificate has expired."
* 2023-09-08 02:13:51 (4102) [[32mINFO[0m] Trying other mirror.
* 2023-09-08 02:13:51 (4102) [[32mINFO[0m] It was impossible to connect to the CentOS servers.
* 2023-09-08 02:13:51 (4102) [[32mINFO[0m] This could mean a connectivity issue in your environment, such as the requirement to configure a proxy,
* 2023-09-08 02:13:51 (4102) [[32mINFO[0m] or a transparent proxy that tampers with TLS security, or an incorrect system clock.
* 2023-09-08 02:13:51 (4102) [[32mINFO[0m] You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors
* 2023-09-08 02:13:51 (4102) [[32mINFO[0m] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2023-09-08 02:13:51 (4102) [[32mINFO[0m] 
* 2023-09-08 02:14:13 (4102) [[32mINFO[0m] 
* 2023-09-08 02:14:13 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-08 02:14:13 (4119) [[32mINFO[0m] 
* 2023-09-08 02:14:13 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-08 02:14:13 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-08 02:14:37 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-08 02:14:37 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FSB5IbVaVf/ea_profile.json
* 2023-09-08 02:14:39 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/FSB5IbVaVf/ea_profile.json
* 2023-09-08 02:14:42 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-08 15:49:30 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-08 15:49:30 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-08 15:49:30 (4089) [[32mINFO[0m] 
* 2023-09-08 15:49:30 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-08 15:49:30 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-08 15:49:30 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-09-08 15:49:30 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-08 15:49:30 (4119) [[32mINFO[0m] 
* 2023-09-08 15:49:30 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-08 15:49:30 (4089) [[32mINFO[0m] 
* 2023-09-08 15:50:06 (4102) [[32mINFO[0m] 
* 2023-09-08 15:50:06 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-08 15:50:06 (4119) [[32mINFO[0m] 
* 2023-09-08 15:50:06 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-08 15:50:06 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-08 15:51:08 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-08 15:51:08 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QWvYHgLFjV/ea_profile.json
* 2023-09-08 15:51:09 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/QWvYHgLFjV/ea_profile.json
* 2023-09-08 15:51:12 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-09 02:14:04 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-09 02:14:04 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-09 02:14:04 (4089) [[32mINFO[0m] 
* 2023-09-09 02:14:04 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-09 02:14:04 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-09 02:14:04 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-09-09 02:14:05 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-09 02:14:05 (4119) [[32mINFO[0m] 
* 2023-09-09 02:14:05 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-09 02:14:05 (4089) [[32mINFO[0m] 
* 2023-09-09 02:14:39 (4102) [[32mINFO[0m] 
* 2023-09-09 02:14:39 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-09 02:14:39 (4119) [[32mINFO[0m] 
* 2023-09-09 02:14:39 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-09 02:14:39 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-09 02:15:05 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-09 02:15:05 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zigBIeN7Jh/ea_profile.json
* 2023-09-09 02:15:07 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/zigBIeN7Jh/ea_profile.json
* 2023-09-09 02:15:10 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-10 02:14:21 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-10 02:14:21 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-10 02:14:21 (4089) [[32mINFO[0m] 
* 2023-09-10 02:14:21 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-10 02:14:21 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-10 02:14:21 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-09-10 02:14:22 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-10 02:14:22 (4119) [[32mINFO[0m] 
* 2023-09-10 02:14:22 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-10 02:14:22 (4089) [[32mINFO[0m] 
* 2023-09-10 02:14:53 (4102) [[32mINFO[0m] 
* 2023-09-10 02:14:53 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-10 02:14:53 (4119) [[32mINFO[0m] 
* 2023-09-10 02:14:53 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-10 02:14:53 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-10 02:15:22 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-10 02:15:22 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/K_MHWgt9XE/ea_profile.json
* 2023-09-10 02:15:24 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/K_MHWgt9XE/ea_profile.json
* 2023-09-10 02:15:28 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-11 02:13:42 (1700) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-11 02:13:42 (4088) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-11 02:13:42 (4089) [[32mINFO[0m] 
* 2023-09-11 02:13:43 (4102) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-11 02:13:43 (4102) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-11 02:13:43 (4102) [[32mINFO[0m]               : epel extras updates
* 2023-09-11 02:13:43 (4102) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-11 02:13:43 (4119) [[32mINFO[0m] 
* 2023-09-11 02:13:43 (4088) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-11 02:13:43 (4089) [[32mINFO[0m] 
* 2023-09-11 02:14:13 (4102) [[32mINFO[0m] 
* 2023-09-11 02:14:13 (4102) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-11 02:14:13 (4119) [[32mINFO[0m] 
* 2023-09-11 02:14:13 (1707) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-11 02:14:13 (153) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-11 02:14:38 (778) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-11 02:14:38 (2236) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FFZRdSSDhc/ea_profile.json
* 2023-09-11 02:14:40 (2259) [[32mINFO[0m] Backed up EA4 profile to /tmp/FFZRdSSDhc/ea_profile.json
* 2023-09-11 02:14:43 (258) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-12 02:13:37 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-12 02:13:37 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-12 02:13:37 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-12 02:13:37 (4229) [[32mINFO[0m] 
* 2023-09-12 02:13:38 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-12 02:13:38 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-12 02:13:38 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-12 02:13:38 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-12 02:13:38 (4259) [[32mINFO[0m] 
* 2023-09-12 02:13:38 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-12 02:13:38 (4229) [[32mINFO[0m] 
* 2023-09-12 02:14:12 (4242) [[32mINFO[0m] 
* 2023-09-12 02:14:12 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-12 02:14:12 (4259) [[32mINFO[0m] 
* 2023-09-12 02:14:12 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-12 02:14:12 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-12 02:16:54 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-12 02:16:54 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dgGIotHyu1/ea_profile.json
* 2023-09-12 02:16:56 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/dgGIotHyu1/ea_profile.json
* 2023-09-12 02:16:59 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-13 02:13:30 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-13 02:13:30 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-13 02:13:30 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-13 02:13:30 (4229) [[32mINFO[0m] 
* 2023-09-13 02:13:31 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-13 02:13:31 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-13 02:13:31 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-13 02:13:31 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-13 02:13:31 (4259) [[32mINFO[0m] 
* 2023-09-13 02:13:31 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-13 02:13:31 (4229) [[32mINFO[0m] 
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m] 12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m] 
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m] 
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m] 
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m] 
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m] 
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m] 
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m] 
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]         or
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m] 
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]         compromise:
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m] 
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m] 
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m] Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2023-09-13 02:14:02 (4259) [[32mINFO[0m] 
* 2023-09-13 02:14:02 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-13 02:14:02 (1773) [[32mINFO[0m] Checking /scripts/sysup
* 2023-09-13 02:14:02 (4228) [[32mINFO[0m] Running: /scripts/sysup
* 2023-09-13 02:14:02 (4229) [[32mINFO[0m] 
* 2023-09-13 02:14:02 (4242) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-09-13 02:14:04 (4242) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-09-13 02:14:04 (4259) [[32mINFO[0m] 
* 2023-09-13 02:14:34 (1618) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-09-13 02:14:34 (1619) [[31mERROR[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2023-09-13 02:14:34 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-13 02:14:35 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-13 02:14:35 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bIEZ31tN80/ea_profile.json
* 2023-09-13 02:14:55 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/bIEZ31tN80/ea_profile.json
* 2023-09-13 02:14:59 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-14 02:15:59 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-14 02:15:59 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-14 02:15:59 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-14 02:15:59 (4229) [[32mINFO[0m] 
* 2023-09-14 02:15:59 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-14 02:15:59 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-14 02:15:59 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-14 02:15:59 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-14 02:15:59 (4259) [[32mINFO[0m] 
* 2023-09-14 02:15:59 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-14 02:15:59 (4229) [[32mINFO[0m] 
* 2023-09-14 02:16:29 (4242) [[32mINFO[0m] 
* 2023-09-14 02:16:29 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-14 02:16:29 (4259) [[32mINFO[0m] 
* 2023-09-14 02:16:29 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-14 02:16:29 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-14 02:16:52 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-14 02:16:52 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dRO6xA1AcX/ea_profile.json
* 2023-09-14 02:16:54 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/dRO6xA1AcX/ea_profile.json
* 2023-09-14 02:16:58 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-15 02:13:35 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-15 02:13:35 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-15 02:13:35 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-15 02:13:35 (4229) [[32mINFO[0m] 
* 2023-09-15 02:13:35 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-15 02:13:35 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-15 02:13:35 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-15 02:13:35 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-15 02:13:35 (4259) [[32mINFO[0m] 
* 2023-09-15 02:13:35 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-15 02:13:35 (4229) [[32mINFO[0m] 
* 2023-09-15 02:14:06 (4242) [[32mINFO[0m] 
* 2023-09-15 02:14:07 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-15 02:14:07 (4259) [[32mINFO[0m] 
* 2023-09-15 02:14:07 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-15 02:14:07 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-15 02:14:31 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-15 02:14:31 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FHMeg3JWd8/ea_profile.json
* 2023-09-15 02:14:32 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/FHMeg3JWd8/ea_profile.json
* 2023-09-15 02:14:35 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-15 15:48:22 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-15 15:48:22 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-15 15:48:22 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-15 15:48:22 (4229) [[32mINFO[0m] 
* 2023-09-15 15:48:23 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-15 15:48:23 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-15 15:48:23 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-15 15:48:23 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-15 15:48:23 (4259) [[32mINFO[0m] 
* 2023-09-15 15:48:23 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-15 15:48:23 (4229) [[32mINFO[0m] 
* 2023-09-15 15:48:52 (4242) [[32mINFO[0m] 
* 2023-09-15 15:48:52 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-15 15:48:52 (4259) [[32mINFO[0m] 
* 2023-09-15 15:48:52 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-15 15:48:52 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-15 15:49:15 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-15 15:49:17 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bRi2Q2VIq2/ea_profile.json
* 2023-09-15 15:49:18 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/bRi2Q2VIq2/ea_profile.json
* 2023-09-15 15:49:22 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-16 02:14:13 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-16 02:14:13 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-16 02:14:13 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-16 02:14:13 (4229) [[32mINFO[0m] 
* 2023-09-16 02:14:13 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-16 02:14:14 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-16 02:14:14 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-16 02:14:14 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-16 02:14:14 (4259) [[32mINFO[0m] 
* 2023-09-16 02:14:14 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-16 02:14:14 (4229) [[32mINFO[0m] 
* 2023-09-16 02:14:46 (4242) [[32mINFO[0m] 
* 2023-09-16 02:14:46 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-16 02:14:46 (4259) [[32mINFO[0m] 
* 2023-09-16 02:14:46 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-16 02:14:46 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-16 02:15:09 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-16 02:15:10 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4Gd2kmNCcT/ea_profile.json
* 2023-09-16 02:15:11 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/4Gd2kmNCcT/ea_profile.json
* 2023-09-16 02:15:15 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-17 02:13:59 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-17 02:13:59 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-17 02:13:59 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-17 02:13:59 (4229) [[32mINFO[0m] 
* 2023-09-17 02:13:59 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-17 02:14:00 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-17 02:14:00 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-17 02:14:00 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-17 02:14:00 (4259) [[32mINFO[0m] 
* 2023-09-17 02:14:00 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-17 02:14:00 (4229) [[32mINFO[0m] 
* 2023-09-17 02:14:31 (4242) [[32mINFO[0m] 
* 2023-09-17 02:14:31 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-17 02:14:31 (4259) [[32mINFO[0m] 
* 2023-09-17 02:14:31 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-17 02:14:31 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-17 02:14:54 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-17 02:14:54 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/eyZJmUuHeq/ea_profile.json
* 2023-09-17 02:14:56 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/eyZJmUuHeq/ea_profile.json
* 2023-09-17 02:15:01 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-18 02:13:28 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-18 02:13:28 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-18 02:13:28 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-18 02:13:28 (4229) [[32mINFO[0m] 
* 2023-09-18 02:13:29 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-18 02:13:29 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-18 02:13:29 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-18 02:13:29 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-18 02:13:29 (4259) [[32mINFO[0m] 
* 2023-09-18 02:13:29 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-18 02:13:29 (4229) [[32mINFO[0m] 
* 2023-09-18 02:14:06 (4242) [[32mINFO[0m] 
* 2023-09-18 02:14:06 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-18 02:14:06 (4259) [[32mINFO[0m] 
* 2023-09-18 02:14:06 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-18 02:14:06 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-18 02:14:27 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-18 02:14:28 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zbjaxoU6KL/ea_profile.json
* 2023-09-18 02:14:29 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/zbjaxoU6KL/ea_profile.json
* 2023-09-18 02:14:34 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-19 02:13:44 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-19 02:13:44 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-19 02:13:44 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-19 02:13:44 (4229) [[32mINFO[0m] 
* 2023-09-19 02:13:44 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-19 02:13:44 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-19 02:13:44 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-19 02:13:45 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-19 02:13:45 (4259) [[32mINFO[0m] 
* 2023-09-19 02:13:45 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-19 02:13:45 (4229) [[32mINFO[0m] 
* 2023-09-19 02:14:17 (4242) [[32mINFO[0m] 
* 2023-09-19 02:14:17 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-19 02:14:17 (4259) [[32mINFO[0m] 
* 2023-09-19 02:14:17 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-19 02:14:17 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-19 02:14:39 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-19 02:14:41 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7YupNMC58s/ea_profile.json
* 2023-09-19 02:14:42 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/7YupNMC58s/ea_profile.json
* 2023-09-19 02:14:46 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-20 02:13:33 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-20 02:13:33 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-20 02:13:33 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-20 02:13:33 (4229) [[32mINFO[0m] 
* 2023-09-20 02:13:33 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-20 02:13:33 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-20 02:13:33 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-20 02:13:34 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-20 02:13:34 (4259) [[32mINFO[0m] 
* 2023-09-20 02:13:34 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-20 02:13:34 (4229) [[32mINFO[0m] 
* 2023-09-20 02:14:03 (4242) [[32mINFO[0m] 
* 2023-09-20 02:14:03 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-20 02:14:03 (4259) [[32mINFO[0m] 
* 2023-09-20 02:14:03 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-20 02:14:03 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-20 02:14:23 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-20 02:14:25 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AX1OI_7xyK/ea_profile.json
* 2023-09-20 02:14:26 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/AX1OI_7xyK/ea_profile.json
* 2023-09-20 02:14:31 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-21 02:15:38 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-21 02:15:38 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-21 02:15:38 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-21 02:15:38 (4229) [[32mINFO[0m] 
* 2023-09-21 02:15:38 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-21 02:15:38 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-21 02:15:38 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-21 02:15:39 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-21 02:15:39 (4259) [[32mINFO[0m] 
* 2023-09-21 02:15:39 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-21 02:15:39 (4229) [[32mINFO[0m] 
* 2023-09-21 02:16:07 (4242) [[32mINFO[0m] 
* 2023-09-21 02:16:07 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-21 02:16:07 (4259) [[32mINFO[0m] 
* 2023-09-21 02:16:07 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-21 02:16:07 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-21 02:16:27 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-21 02:16:27 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6ikJZCj2bF/ea_profile.json
* 2023-09-21 02:16:29 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/6ikJZCj2bF/ea_profile.json
* 2023-09-21 02:16:36 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-22 02:14:25 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-22 02:14:25 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-22 02:14:25 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-22 02:14:25 (4229) [[32mINFO[0m] 
* 2023-09-22 02:14:25 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-22 02:14:25 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-22 02:14:25 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-22 02:14:25 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-22 02:14:25 (4259) [[32mINFO[0m] 
* 2023-09-22 02:14:25 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-22 02:14:25 (4229) [[32mINFO[0m] 
* 2023-09-22 02:15:13 (4242) [[32mINFO[0m] 
* 2023-09-22 02:15:13 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-22 02:15:13 (4259) [[32mINFO[0m] 
* 2023-09-22 02:15:13 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-22 02:15:13 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-22 02:15:43 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-22 02:15:43 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NwtXbu1gcb/ea_profile.json
* 2023-09-22 02:15:45 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/NwtXbu1gcb/ea_profile.json
* 2023-09-22 02:15:48 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-22 15:48:13 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-22 15:48:13 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-22 15:48:13 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-22 15:48:13 (4229) [[32mINFO[0m] 
* 2023-09-22 15:48:13 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-22 15:48:13 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-22 15:48:13 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-22 15:48:13 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-22 15:48:13 (4259) [[32mINFO[0m] 
* 2023-09-22 15:48:13 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-22 15:48:13 (4229) [[32mINFO[0m] 
* 2023-09-22 15:48:43 (4242) [[32mINFO[0m] 
* 2023-09-22 15:48:43 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-22 15:48:44 (4259) [[32mINFO[0m] 
* 2023-09-22 15:48:44 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-22 15:48:44 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-22 15:49:12 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-22 15:49:12 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EX6nfuHYpo/ea_profile.json
* 2023-09-22 15:49:13 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/EX6nfuHYpo/ea_profile.json
* 2023-09-22 15:49:17 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-23 02:13:54 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-23 02:13:54 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-23 02:13:54 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-23 02:13:54 (4229) [[32mINFO[0m] 
* 2023-09-23 02:13:54 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-23 02:13:54 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-23 02:13:54 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-23 02:13:54 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-23 02:13:54 (4259) [[32mINFO[0m] 
* 2023-09-23 02:13:54 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-23 02:13:54 (4229) [[32mINFO[0m] 
* 2023-09-23 02:14:24 (4242) [[32mINFO[0m] 
* 2023-09-23 02:14:24 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-23 02:14:24 (4259) [[32mINFO[0m] 
* 2023-09-23 02:14:24 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-23 02:14:24 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-23 02:14:45 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-23 02:14:45 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lo_qc1Xwke/ea_profile.json
* 2023-09-23 02:14:46 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/lo_qc1Xwke/ea_profile.json
* 2023-09-23 02:14:53 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-24 02:13:53 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-24 02:13:53 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-24 02:13:53 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-24 02:13:53 (4229) [[32mINFO[0m] 
* 2023-09-24 02:13:54 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-24 02:13:54 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-24 02:13:54 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-24 02:13:54 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-24 02:13:54 (4259) [[32mINFO[0m] 
* 2023-09-24 02:13:54 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-24 02:13:54 (4229) [[32mINFO[0m] 
* 2023-09-24 02:14:24 (4242) [[32mINFO[0m] 
* 2023-09-24 02:14:24 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-24 02:14:25 (4259) [[32mINFO[0m] 
* 2023-09-24 02:14:25 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-24 02:14:25 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-24 02:14:44 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-24 02:14:46 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9Es7sDGVHW/ea_profile.json
* 2023-09-24 02:14:47 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/9Es7sDGVHW/ea_profile.json
* 2023-09-24 02:14:51 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-25 02:13:28 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-25 02:13:28 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-25 02:13:28 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-25 02:13:28 (4229) [[32mINFO[0m] 
* 2023-09-25 02:13:29 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-25 02:13:29 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-25 02:13:29 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-25 02:13:29 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-25 02:13:29 (4259) [[32mINFO[0m] 
* 2023-09-25 02:13:29 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-25 02:13:29 (4229) [[32mINFO[0m] 
* 2023-09-25 02:14:00 (4242) [[32mINFO[0m] 
* 2023-09-25 02:14:00 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-25 02:14:00 (4259) [[32mINFO[0m] 
* 2023-09-25 02:14:01 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-25 02:14:01 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-25 02:14:25 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-25 02:14:25 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GjuB5OU5hq/ea_profile.json
* 2023-09-25 02:14:26 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/GjuB5OU5hq/ea_profile.json
* 2023-09-25 02:14:30 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-26 02:13:05 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-26 02:13:05 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-26 02:13:05 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-26 02:13:05 (4229) [[32mINFO[0m] 
* 2023-09-26 02:13:05 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-26 02:13:05 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-26 02:13:05 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-26 02:13:06 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-26 02:13:06 (4259) [[32mINFO[0m] 
* 2023-09-26 02:13:06 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-26 02:13:06 (4229) [[32mINFO[0m] 
* 2023-09-26 02:13:33 (4242) [[32mINFO[0m] 
* 2023-09-26 02:13:33 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-26 02:13:33 (4259) [[32mINFO[0m] 
* 2023-09-26 02:13:33 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-26 02:13:33 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-26 02:13:53 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-26 02:13:56 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UUrNvitnd3/ea_profile.json
* 2023-09-26 02:13:57 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/UUrNvitnd3/ea_profile.json
* 2023-09-26 02:14:00 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-27 02:14:18 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-27 02:14:18 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-27 02:14:18 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-27 02:14:18 (4229) [[32mINFO[0m] 
* 2023-09-27 02:14:19 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-27 02:14:19 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-27 02:14:19 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-27 02:14:19 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-27 02:14:19 (4259) [[32mINFO[0m] 
* 2023-09-27 02:14:19 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-27 02:14:19 (4229) [[32mINFO[0m] 
* 2023-09-27 02:15:03 (4242) [[32mINFO[0m] 
* 2023-09-27 02:15:03 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-27 02:15:03 (4259) [[32mINFO[0m] 
* 2023-09-27 02:15:03 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-27 02:15:03 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-27 02:15:49 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-27 02:15:49 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2o5ZkPku50/ea_profile.json
* 2023-09-27 02:15:51 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/2o5ZkPku50/ea_profile.json
* 2023-09-27 02:15:54 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-28 02:15:33 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-28 02:15:33 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-28 02:15:33 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-28 02:15:33 (4229) [[32mINFO[0m] 
* 2023-09-28 02:15:33 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-28 02:15:33 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-28 02:15:33 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-28 02:15:33 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-28 02:15:33 (4259) [[32mINFO[0m] 
* 2023-09-28 02:15:33 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-28 02:15:33 (4229) [[32mINFO[0m] 
* 2023-09-28 02:17:24 (4242) [[32mINFO[0m] 
* 2023-09-28 02:17:24 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-28 02:17:24 (4259) [[32mINFO[0m] 
* 2023-09-28 02:17:24 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-28 02:17:24 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-28 02:18:06 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-28 02:18:06 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/N0l7pFKwnG/ea_profile.json
* 2023-09-28 02:18:08 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/N0l7pFKwnG/ea_profile.json
* 2023-09-28 02:18:11 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-29 02:13:50 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-29 02:13:50 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-29 02:13:50 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-29 02:13:50 (4229) [[32mINFO[0m] 
* 2023-09-29 02:13:50 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-29 02:13:50 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-29 02:13:50 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-29 02:13:50 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-29 02:13:50 (4259) [[32mINFO[0m] 
* 2023-09-29 02:13:50 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-29 02:13:50 (4229) [[32mINFO[0m] 
* 2023-09-29 02:14:45 (4242) [[32mINFO[0m] 
* 2023-09-29 02:14:45 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-29 02:14:45 (4259) [[32mINFO[0m] 
* 2023-09-29 02:14:45 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-29 02:14:45 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-29 02:15:22 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-29 02:15:22 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Rrf4JhLJee/ea_profile.json
* 2023-09-29 02:15:24 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/Rrf4JhLJee/ea_profile.json
* 2023-09-29 02:15:28 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-29 15:48:41 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-29 15:48:41 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-29 15:48:41 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-29 15:48:41 (4229) [[32mINFO[0m] 
* 2023-09-29 15:48:41 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-29 15:48:41 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-29 15:48:41 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-29 15:48:41 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-29 15:48:41 (4259) [[32mINFO[0m] 
* 2023-09-29 15:48:41 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-29 15:48:41 (4229) [[32mINFO[0m] 
* 2023-09-29 15:48:52 (4242) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/91495e579330470fb1bef143824e46c2eba2e380fa44ef6cb2a59082601b7702-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-09-29 15:48:52 (4242) [[32mINFO[0m] Trying other mirror.
* 2023-09-29 15:48:52 (4242) [[32mINFO[0m] To address this issue please refer to the below wiki article 
* 2023-09-29 15:48:52 (4242) [[32mINFO[0m] 
* 2023-09-29 15:48:52 (4242) [[32mINFO[0m] https://wiki.centos.org/yum-errors
* 2023-09-29 15:48:52 (4242) [[32mINFO[0m] 
* 2023-09-29 15:48:52 (4242) [[32mINFO[0m] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2023-09-29 15:48:52 (4242) [[32mINFO[0m] 
* 2023-09-29 15:49:12 (4242) [[32mINFO[0m] 
* 2023-09-29 15:49:12 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-29 15:49:12 (4259) [[32mINFO[0m] 
* 2023-09-29 15:49:12 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-29 15:49:12 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-29 15:49:48 (1618) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-09-29 15:49:48 (1619) [[31mERROR[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/36688a58bcbfabedc120b1d34a1be3ef597e83d134e9f316d9966b84b576e847-filelists.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-09-29 15:49:48 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-29 15:49:49 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-29 15:49:49 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WsKE0j_RkV/ea_profile.json
* 2023-09-29 15:49:50 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/WsKE0j_RkV/ea_profile.json
* 2023-09-29 15:49:53 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-30 02:14:36 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-09-30 02:14:36 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-09-30 02:14:36 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-09-30 02:14:36 (4229) [[32mINFO[0m] 
* 2023-09-30 02:14:36 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-30 02:14:36 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-09-30 02:14:36 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-09-30 02:14:36 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-09-30 02:14:36 (4259) [[32mINFO[0m] 
* 2023-09-30 02:14:36 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-09-30 02:14:36 (4229) [[32mINFO[0m] 
* 2023-09-30 02:15:34 (4242) [[32mINFO[0m] 
* 2023-09-30 02:15:34 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-30 02:15:34 (4259) [[32mINFO[0m] 
* 2023-09-30 02:15:34 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-30 02:15:34 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-30 02:16:18 (1618) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-09-30 02:16:18 (1619) [[31mERROR[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/54e1624b92dc757ff7ab0a3ff70fc22b4dbc8b5f754e66d77a30a4836942288c-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-09-30 02:16:18 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-30 02:16:19 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-30 02:16:19 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Q12ktxJReW/ea_profile.json
* 2023-09-30 02:16:20 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/Q12ktxJReW/ea_profile.json
* 2023-09-30 02:16:24 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-01 02:13:42 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-01 02:13:42 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-01 02:13:42 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-01 02:13:42 (4229) [[32mINFO[0m] 
* 2023-10-01 02:13:42 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-01 02:13:42 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-01 02:13:42 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-01 02:13:42 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-01 02:13:42 (4259) [[32mINFO[0m] 
* 2023-10-01 02:13:42 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-01 02:13:42 (4229) [[32mINFO[0m] 
* 2023-10-01 02:14:11 (4242) [[32mINFO[0m] 
* 2023-10-01 02:14:11 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-01 02:14:11 (4259) [[32mINFO[0m] 
* 2023-10-01 02:14:11 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-01 02:14:11 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-01 02:14:32 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-01 02:14:33 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fnsBZfttpx/ea_profile.json
* 2023-10-01 02:14:35 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/fnsBZfttpx/ea_profile.json
* 2023-10-01 02:14:40 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-02 02:13:17 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-02 02:13:17 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-02 02:13:17 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-02 02:13:17 (4229) [[32mINFO[0m] 
* 2023-10-02 02:13:17 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-02 02:13:18 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-02 02:13:18 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-02 02:13:18 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-02 02:13:18 (4259) [[32mINFO[0m] 
* 2023-10-02 02:13:18 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-02 02:13:18 (4229) [[32mINFO[0m] 
* 2023-10-02 02:13:51 (4242) [[32mINFO[0m] 
* 2023-10-02 02:13:51 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-02 02:13:51 (4259) [[32mINFO[0m] 
* 2023-10-02 02:13:51 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-02 02:13:51 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-02 02:14:19 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-02 02:14:19 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QixJsI2qzX/ea_profile.json
* 2023-10-02 02:14:20 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/QixJsI2qzX/ea_profile.json
* 2023-10-02 02:14:24 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-03 02:40:22 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-03 02:40:22 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-03 02:40:22 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-03 02:40:22 (4229) [[32mINFO[0m] 
* 2023-10-03 02:40:22 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-03 02:40:22 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-03 02:40:22 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-03 02:40:22 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-03 02:40:22 (4259) [[32mINFO[0m] 
* 2023-10-03 02:40:22 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-03 02:40:22 (4229) [[32mINFO[0m] 
* 2023-10-03 02:40:52 (4242) [[32mINFO[0m] 
* 2023-10-03 02:40:52 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-03 02:40:52 (4259) [[32mINFO[0m] 
* 2023-10-03 02:40:52 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-03 02:40:52 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-03 02:41:14 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-03 02:41:14 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XulKnbWbIm/ea_profile.json
* 2023-10-03 02:41:16 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/XulKnbWbIm/ea_profile.json
* 2023-10-03 02:41:18 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-04 02:16:06 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-10-04 02:16:07 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-04 02:16:07 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-04 02:16:07 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-04 02:16:07 (4229) [[32mINFO[0m] 
* 2023-10-04 02:16:07 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-04 02:16:07 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-04 02:16:07 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-04 02:16:08 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-04 02:16:08 (4259) [[32mINFO[0m] 
* 2023-10-04 02:16:08 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-04 02:16:08 (4229) [[32mINFO[0m] 
* 2023-10-04 02:17:12 (4242) [[32mINFO[0m] 
* 2023-10-04 02:17:12 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-04 02:17:12 (4259) [[32mINFO[0m] 
* 2023-10-04 02:17:12 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-04 02:17:12 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-04 02:17:55 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-04 02:17:55 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7z6DunwTj1/ea_profile.json
* 2023-10-04 02:17:57 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/7z6DunwTj1/ea_profile.json
* 2023-10-04 02:17:59 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-05 02:15:21 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-05 02:15:21 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-05 02:15:21 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-05 02:15:21 (4229) [[32mINFO[0m] 
* 2023-10-05 02:15:21 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-05 02:15:21 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-05 02:15:21 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-05 02:15:21 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-05 02:15:21 (4259) [[32mINFO[0m] 
* 2023-10-05 02:15:21 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-05 02:15:21 (4229) [[32mINFO[0m] 
* 2023-10-05 02:16:22 (4242) [[32mINFO[0m] 
* 2023-10-05 02:16:22 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-05 02:16:22 (4259) [[32mINFO[0m] 
* 2023-10-05 02:16:22 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-05 02:16:22 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-05 02:16:59 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-05 02:17:00 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dBQBjKuFMc/ea_profile.json
* 2023-10-05 02:17:01 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/dBQBjKuFMc/ea_profile.json
* 2023-10-05 02:17:04 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-06 02:13:49 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-06 02:13:49 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-06 02:13:49 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-06 02:13:49 (4229) [[32mINFO[0m] 
* 2023-10-06 02:13:49 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-06 02:13:49 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-06 02:13:49 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-06 02:13:49 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-06 02:13:49 (4259) [[32mINFO[0m] 
* 2023-10-06 02:13:49 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-06 02:13:49 (4229) [[32mINFO[0m] 
* 2023-10-06 02:14:29 (4242) [[32mINFO[0m] 
* 2023-10-06 02:14:29 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-06 02:14:29 (4259) [[32mINFO[0m] 
* 2023-10-06 02:14:29 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-06 02:14:29 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-06 02:15:37 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-06 02:15:37 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ALNABqZNOg/ea_profile.json
* 2023-10-06 02:15:39 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/ALNABqZNOg/ea_profile.json
* 2023-10-06 02:15:41 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-06 15:48:47 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-06 15:48:47 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-06 15:48:47 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-06 15:48:47 (4229) [[32mINFO[0m] 
* 2023-10-06 15:48:47 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-06 15:48:47 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-06 15:48:47 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-06 15:48:47 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-06 15:48:47 (4259) [[32mINFO[0m] 
* 2023-10-06 15:48:47 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-06 15:48:47 (4229) [[32mINFO[0m] 
* 2023-10-06 15:51:17 (4242) [[32mINFO[0m] 
* 2023-10-06 15:51:17 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-06 15:51:17 (4259) [[32mINFO[0m] 
* 2023-10-06 15:51:17 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-06 15:51:17 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-06 15:51:44 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-06 15:51:44 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/K8LpiaEZlW/ea_profile.json
* 2023-10-06 15:51:45 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/K8LpiaEZlW/ea_profile.json
* 2023-10-06 15:51:48 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-07 02:15:09 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-07 02:15:09 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-07 02:15:09 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-07 02:15:09 (4229) [[32mINFO[0m] 
* 2023-10-07 02:15:09 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-07 02:15:09 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-07 02:15:09 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-07 02:15:09 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-07 02:15:09 (4259) [[32mINFO[0m] 
* 2023-10-07 02:15:09 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-07 02:15:09 (4229) [[32mINFO[0m] 
* 2023-10-07 02:16:06 (4242) [[32mINFO[0m] 
* 2023-10-07 02:16:06 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-07 02:16:06 (4259) [[32mINFO[0m] 
* 2023-10-07 02:16:06 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-07 02:16:06 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-07 02:16:50 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-07 02:16:50 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XZeH_7sPkh/ea_profile.json
* 2023-10-07 02:16:51 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/XZeH_7sPkh/ea_profile.json
* 2023-10-07 02:16:54 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-08 02:13:38 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-08 02:13:38 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-08 02:13:38 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-08 02:13:38 (4229) [[32mINFO[0m] 
* 2023-10-08 02:13:39 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-08 02:13:39 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-08 02:13:39 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-08 02:13:39 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-08 02:13:39 (4259) [[32mINFO[0m] 
* 2023-10-08 02:13:39 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-08 02:13:39 (4229) [[32mINFO[0m] 
* 2023-10-08 02:14:10 (4242) [[32mINFO[0m] 
* 2023-10-08 02:14:10 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-08 02:14:11 (4259) [[32mINFO[0m] 
* 2023-10-08 02:14:11 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-08 02:14:11 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-08 02:14:44 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-08 02:14:44 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SGdpHVDbPG/ea_profile.json
* 2023-10-08 02:14:45 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/SGdpHVDbPG/ea_profile.json
* 2023-10-08 02:14:48 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-09 02:13:27 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-09 02:13:27 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-09 02:13:27 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-09 02:13:27 (4229) [[32mINFO[0m] 
* 2023-10-09 02:13:28 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-09 02:13:28 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-09 02:13:28 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-09 02:13:28 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-09 02:13:28 (4259) [[32mINFO[0m] 
* 2023-10-09 02:13:28 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-09 02:13:28 (4229) [[32mINFO[0m] 
* 2023-10-09 02:14:13 (4242) [[32mINFO[0m] https://mirror.nyist.edu.cn/epel/7/x86_64/repodata/f1b6dd4a1e02d1de89fda8533630cd6bab2ef98fc6fc73600b7ea62a66bec092-primary.sqlite.bz2: [Errno 12] Timeout on https://mirror.nyist.edu.cn/epel/7/x86_64/repodata/f1b6dd4a1e02d1de89fda8533630cd6bab2ef98fc6fc73600b7ea62a66bec092-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-10-09 02:14:13 (4242) [[32mINFO[0m] Trying other mirror.
* 2023-10-09 02:14:29 (4242) [[32mINFO[0m] 
* 2023-10-09 02:14:29 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-09 02:14:29 (4259) [[32mINFO[0m] 
* 2023-10-09 02:14:29 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-09 02:14:29 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-09 02:14:49 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-09 02:14:49 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ugXM6BcVIr/ea_profile.json
* 2023-10-09 02:14:50 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/ugXM6BcVIr/ea_profile.json
* 2023-10-09 02:14:53 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-10 02:17:32 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-10 02:17:32 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-10 02:17:32 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-10 02:17:32 (4229) [[32mINFO[0m] 
* 2023-10-10 02:17:32 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-10 02:17:32 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-10 02:17:32 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-10 02:17:33 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-10 02:17:33 (4259) [[32mINFO[0m] 
* 2023-10-10 02:17:33 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-10 02:17:33 (4229) [[32mINFO[0m] 
* 2023-10-10 02:18:10 (4242) [[32mINFO[0m] 
* 2023-10-10 02:18:10 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-10 02:18:10 (4259) [[32mINFO[0m] 
* 2023-10-10 02:18:10 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-10 02:18:10 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-10 02:18:34 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-10 02:18:34 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QBC0PgHzWP/ea_profile.json
* 2023-10-10 02:18:35 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/QBC0PgHzWP/ea_profile.json
* 2023-10-10 02:18:38 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-11 02:13:22 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-11 02:13:22 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-11 02:13:22 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-11 02:13:22 (4229) [[32mINFO[0m] 
* 2023-10-11 02:13:23 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-11 02:13:23 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-11 02:13:23 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-11 02:13:23 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-11 02:13:23 (4259) [[32mINFO[0m] 
* 2023-10-11 02:13:23 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-11 02:13:23 (4229) [[32mINFO[0m] 
* 2023-10-11 02:13:54 (4242) [[32mINFO[0m] 
* 2023-10-11 02:13:54 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-11 02:13:54 (4259) [[32mINFO[0m] 
* 2023-10-11 02:13:54 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-11 02:13:54 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-11 02:14:20 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-11 02:14:20 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MICtVVuBau/ea_profile.json
* 2023-10-11 02:14:21 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/MICtVVuBau/ea_profile.json
* 2023-10-11 02:14:24 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-12 02:13:58 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-12 02:13:58 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-12 02:13:58 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-12 02:13:58 (4229) [[32mINFO[0m] 
* 2023-10-12 02:13:58 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-12 02:13:58 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-12 02:13:58 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-12 02:13:58 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-12 02:13:58 (4259) [[32mINFO[0m] 
* 2023-10-12 02:13:58 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-12 02:13:58 (4229) [[32mINFO[0m] 
* 2023-10-12 02:14:24 (4242) [[32mINFO[0m] 
* 2023-10-12 02:14:24 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-12 02:14:24 (4259) [[32mINFO[0m] 
* 2023-10-12 02:14:24 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-12 02:14:24 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-12 02:14:48 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-12 02:14:48 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QMoS2DaJGd/ea_profile.json
* 2023-10-12 02:14:50 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/QMoS2DaJGd/ea_profile.json
* 2023-10-12 02:14:52 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-13 02:15:36 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-13 02:15:36 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-13 02:15:36 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-13 02:15:36 (4229) [[32mINFO[0m] 
* 2023-10-13 02:15:36 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-13 02:15:36 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-13 02:15:36 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-13 02:15:36 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-13 02:15:37 (4259) [[32mINFO[0m] 
* 2023-10-13 02:15:37 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-13 02:15:37 (4229) [[32mINFO[0m] 
* 2023-10-13 02:18:27 (4242) [[32mINFO[0m] 
* 2023-10-13 02:18:27 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-13 02:18:27 (4259) [[32mINFO[0m] 
* 2023-10-13 02:18:27 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-13 02:18:27 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-13 02:19:08 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-13 02:19:08 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lXXqTpAlCG/ea_profile.json
* 2023-10-13 02:19:09 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/lXXqTpAlCG/ea_profile.json
* 2023-10-13 02:19:12 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-13 15:48:19 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-13 15:48:19 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-13 15:48:19 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-13 15:48:19 (4229) [[32mINFO[0m] 
* 2023-10-13 15:48:19 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-13 15:48:19 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-13 15:48:19 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-13 15:48:20 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-13 15:48:20 (4259) [[32mINFO[0m] 
* 2023-10-13 15:48:20 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-13 15:48:20 (4229) [[32mINFO[0m] 
* 2023-10-13 15:48:53 (4242) [[32mINFO[0m] 
* 2023-10-13 15:48:53 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-13 15:48:54 (4259) [[32mINFO[0m] 
* 2023-10-13 15:48:54 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-13 15:48:54 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-13 15:49:17 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-13 15:49:17 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ew4irMguEV/ea_profile.json
* 2023-10-13 15:49:19 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/Ew4irMguEV/ea_profile.json
* 2023-10-13 15:49:21 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-14 02:15:35 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-14 02:15:35 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-14 02:15:35 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-14 02:15:35 (4229) [[32mINFO[0m] 
* 2023-10-14 02:15:36 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-14 02:15:36 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-14 02:15:36 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-14 02:15:36 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-14 02:15:36 (4259) [[32mINFO[0m] 
* 2023-10-14 02:15:36 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-14 02:15:36 (4229) [[32mINFO[0m] 
* 2023-10-14 02:16:46 (4242) [[32mINFO[0m] https://mirror.yer.az/fedora-epel/7/x86_64/repodata/748f422618d1cf4753622efb58005e55a0412282a1a3db57c5e5d9f3a248c2ad-comps-Everything.x86_64.xml.gz: [Errno 12] Timeout on https://mirror.yer.az/fedora-epel/7/x86_64/repodata/748f422618d1cf4753622efb58005e55a0412282a1a3db57c5e5d9f3a248c2ad-comps-Everything.x86_64.xml.gz: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
* 2023-10-14 02:16:46 (4242) [[32mINFO[0m] Trying other mirror.
* 2023-10-14 02:17:23 (4242) [[32mINFO[0m] 
* 2023-10-14 02:17:23 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-14 02:17:23 (4259) [[32mINFO[0m] 
* 2023-10-14 02:17:23 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-14 02:17:23 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-14 02:18:34 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-14 02:18:34 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6FxLVd02fd/ea_profile.json
* 2023-10-14 02:18:36 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/6FxLVd02fd/ea_profile.json
* 2023-10-14 02:18:39 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-15 02:15:33 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-15 02:15:33 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-15 02:15:33 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-15 02:15:33 (4229) [[32mINFO[0m] 
* 2023-10-15 02:15:33 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-15 02:15:34 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-15 02:15:34 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-15 02:15:34 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-15 02:15:34 (4259) [[32mINFO[0m] 
* 2023-10-15 02:15:34 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-15 02:15:34 (4229) [[32mINFO[0m] 
* 2023-10-15 02:16:39 (4242) [[32mINFO[0m] https://mirror.yer.az/fedora-epel/7/x86_64/repodata/748f422618d1cf4753622efb58005e55a0412282a1a3db57c5e5d9f3a248c2ad-comps-Everything.x86_64.xml.gz: [Errno 12] Timeout on https://mirror.yer.az/fedora-epel/7/x86_64/repodata/748f422618d1cf4753622efb58005e55a0412282a1a3db57c5e5d9f3a248c2ad-comps-Everything.x86_64.xml.gz: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')
* 2023-10-15 02:16:39 (4242) [[32mINFO[0m] Trying other mirror.
* 2023-10-15 02:16:55 (4242) [[32mINFO[0m] 
* 2023-10-15 02:16:55 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-15 02:16:55 (4259) [[32mINFO[0m] 
* 2023-10-15 02:16:55 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-15 02:16:55 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-15 02:17:19 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-15 02:17:19 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iXkglr6e21/ea_profile.json
* 2023-10-15 02:17:21 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/iXkglr6e21/ea_profile.json
* 2023-10-15 02:17:23 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-16 02:13:05 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-16 02:13:05 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-16 02:13:05 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-16 02:13:05 (4229) [[32mINFO[0m] 
* 2023-10-16 02:13:06 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-16 02:13:06 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-16 02:13:06 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-16 02:13:06 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-16 02:13:06 (4259) [[32mINFO[0m] 
* 2023-10-16 02:13:06 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-16 02:13:06 (4229) [[32mINFO[0m] 
* 2023-10-16 02:13:36 (4242) [[32mINFO[0m] 
* 2023-10-16 02:13:36 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-16 02:13:36 (4259) [[32mINFO[0m] 
* 2023-10-16 02:13:36 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-16 02:13:36 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-16 02:13:59 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-16 02:13:59 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6DhYutD5Xx/ea_profile.json
* 2023-10-16 02:14:01 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/6DhYutD5Xx/ea_profile.json
* 2023-10-16 02:14:03 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-17 02:13:53 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-17 02:13:53 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-17 02:13:53 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-17 02:13:53 (4229) [[32mINFO[0m] 
* 2023-10-17 02:13:53 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-17 02:13:53 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-17 02:13:53 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-17 02:13:54 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-17 02:13:54 (4259) [[32mINFO[0m] 
* 2023-10-17 02:13:54 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-17 02:13:54 (4229) [[32mINFO[0m] 
* 2023-10-17 02:14:22 (4242) [[32mINFO[0m] 
* 2023-10-17 02:14:22 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-17 02:14:22 (4259) [[32mINFO[0m] 
* 2023-10-17 02:14:22 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-17 02:14:22 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-17 02:14:41 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-17 02:14:41 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KmZdZwCrdu/ea_profile.json
* 2023-10-17 02:14:43 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/KmZdZwCrdu/ea_profile.json
* 2023-10-17 02:14:45 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-18 02:13:04 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-18 02:13:04 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-18 02:13:04 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-18 02:13:04 (4229) [[32mINFO[0m] 
* 2023-10-18 02:13:04 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-18 02:13:04 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-18 02:13:04 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-18 02:13:04 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-18 02:13:05 (4259) [[32mINFO[0m] 
* 2023-10-18 02:13:05 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-18 02:13:05 (4229) [[32mINFO[0m] 
* 2023-10-18 02:13:32 (4242) [[32mINFO[0m] 
* 2023-10-18 02:13:32 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-18 02:13:33 (4259) [[32mINFO[0m] 
* 2023-10-18 02:13:33 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-18 02:13:33 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-18 02:13:53 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-18 02:13:53 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tW7ZIdn84b/ea_profile.json
* 2023-10-18 02:13:54 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/tW7ZIdn84b/ea_profile.json
* 2023-10-18 02:13:57 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-19 02:14:09 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-19 02:14:09 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-19 02:14:09 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-19 02:14:09 (4229) [[32mINFO[0m] 
* 2023-10-19 02:14:09 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-19 02:14:09 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-19 02:14:09 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-19 02:14:09 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-19 02:14:09 (4259) [[32mINFO[0m] 
* 2023-10-19 02:14:09 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-19 02:14:09 (4229) [[32mINFO[0m] 
* 2023-10-19 02:15:12 (4242) [[32mINFO[0m] 
* 2023-10-19 02:15:12 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-19 02:15:12 (4259) [[32mINFO[0m] 
* 2023-10-19 02:15:12 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-19 02:15:12 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-19 02:16:09 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-19 02:16:09 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/W7X263S3KP/ea_profile.json
* 2023-10-19 02:16:11 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/W7X263S3KP/ea_profile.json
* 2023-10-19 02:16:13 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-20 02:14:38 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-20 02:14:38 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-20 02:14:38 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-20 02:14:38 (4229) [[32mINFO[0m] 
* 2023-10-20 02:14:39 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-20 02:14:39 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-20 02:14:39 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-20 02:14:39 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-20 02:14:39 (4259) [[32mINFO[0m] 
* 2023-10-20 02:14:39 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-20 02:14:39 (4229) [[32mINFO[0m] 
* 2023-10-20 02:15:35 (4242) [[32mINFO[0m] 
* 2023-10-20 02:15:35 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-20 02:15:35 (4259) [[32mINFO[0m] 
* 2023-10-20 02:15:35 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-20 02:15:35 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-20 02:16:21 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-20 02:16:21 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XuB663l7bc/ea_profile.json
* 2023-10-20 02:16:23 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/XuB663l7bc/ea_profile.json
* 2023-10-20 02:16:26 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-20 15:50:11 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-10-20 15:50:12 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-20 15:50:12 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-20 15:50:12 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-20 15:50:12 (4229) [[32mINFO[0m] 
* 2023-10-20 15:50:12 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-20 15:50:12 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-20 15:50:12 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-20 15:50:13 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-20 15:50:13 (4259) [[32mINFO[0m] 
* 2023-10-20 15:50:13 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-20 15:50:13 (4229) [[32mINFO[0m] 
* 2023-10-20 15:51:11 (4242) [[32mINFO[0m] 
* 2023-10-20 15:51:11 (4242) [[32mINFO[0m] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-20 15:51:11 (4259) [[32mINFO[0m] 
* 2023-10-20 15:51:11 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-20 15:51:11 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-20 15:51:57 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-20 15:51:57 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qhF7F1Fl6g/ea_profile.json
* 2023-10-20 15:51:59 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/qhF7F1Fl6g/ea_profile.json
* 2023-10-20 15:52:01 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-21 02:15:21 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-21 02:15:21 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-21 02:15:21 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-21 02:15:21 (4229) [[32mINFO[0m] 
* 2023-10-21 02:15:21 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-21 02:15:21 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-21 02:15:21 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-21 02:15:21 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-21 02:15:21 (4259) [[32mINFO[0m] 
* 2023-10-21 02:15:21 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-21 02:15:21 (4229) [[32mINFO[0m] 
* 2023-10-21 02:15:53 (4242) [[32mINFO[0m] 
* 2023-10-21 02:15:53 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-21 02:15:53 (4259) [[32mINFO[0m] 
* 2023-10-21 02:15:53 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-21 02:15:53 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-21 02:16:18 (1618) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-10-21 02:16:18 (1619) [[31mERROR[0m] https://mirror.yer.az/fedora-epel/7/x86_64/repodata/a602324f510358660e3ee49188d17e3eb2b92b6206488aa8ea4ac8a86197b232-filelists.sqlite.bz2: [Errno 14] curl#35 - "Encountered end of file"
Trying other mirror.
* 2023-10-21 02:16:18 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-21 02:16:19 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-21 02:16:19 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JDQ96edqEU/ea_profile.json
* 2023-10-21 02:16:20 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/JDQ96edqEU/ea_profile.json
* 2023-10-21 02:16:23 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-22 02:13:51 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-22 02:13:51 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-22 02:13:51 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-22 02:13:51 (4229) [[32mINFO[0m] 
* 2023-10-22 02:13:51 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-22 02:13:51 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-22 02:13:51 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-22 02:13:51 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-22 02:13:51 (4259) [[32mINFO[0m] 
* 2023-10-22 02:13:51 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-22 02:13:51 (4229) [[32mINFO[0m] 
* 2023-10-22 02:14:25 (4242) [[32mINFO[0m] 
* 2023-10-22 02:14:25 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-22 02:14:25 (4259) [[32mINFO[0m] 
* 2023-10-22 02:14:25 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-22 02:14:25 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-22 02:14:50 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-22 02:14:50 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7bAxqmYltu/ea_profile.json
* 2023-10-22 02:14:51 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/7bAxqmYltu/ea_profile.json
* 2023-10-22 02:14:54 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-23 02:13:21 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-23 02:13:21 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-23 02:13:21 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-23 02:13:21 (4229) [[32mINFO[0m] 
* 2023-10-23 02:13:21 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-23 02:13:21 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-23 02:13:21 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-23 02:13:21 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-23 02:13:21 (4259) [[32mINFO[0m] 
* 2023-10-23 02:13:21 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-23 02:13:21 (4229) [[32mINFO[0m] 
* 2023-10-23 02:13:56 (4242) [[32mINFO[0m] 
* 2023-10-23 02:13:56 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-23 02:13:56 (4259) [[32mINFO[0m] 
* 2023-10-23 02:13:56 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-23 02:13:56 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-23 02:14:21 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-23 02:14:21 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZiO0Eqxnky/ea_profile.json
* 2023-10-23 02:14:22 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/ZiO0Eqxnky/ea_profile.json
* 2023-10-23 02:14:25 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-24 02:13:23 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-24 02:13:23 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-24 02:13:23 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-24 02:13:23 (4229) [[32mINFO[0m] 
* 2023-10-24 02:13:24 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-24 02:13:24 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-24 02:13:24 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-24 02:13:24 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-24 02:13:24 (4259) [[32mINFO[0m] 
* 2023-10-24 02:13:24 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-24 02:13:24 (4229) [[32mINFO[0m] 
* 2023-10-24 02:13:54 (4242) [[32mINFO[0m] 
* 2023-10-24 02:13:54 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-24 02:13:54 (4259) [[32mINFO[0m] 
* 2023-10-24 02:13:54 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-24 02:13:54 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-24 02:14:18 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-24 02:14:18 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Lr4c9fBLps/ea_profile.json
* 2023-10-24 02:14:19 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/Lr4c9fBLps/ea_profile.json
* 2023-10-24 02:14:22 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-25 02:13:24 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-25 02:13:24 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-25 02:13:24 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-25 02:13:24 (4229) [[32mINFO[0m] 
* 2023-10-25 02:13:24 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-25 02:13:24 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-25 02:13:24 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-25 02:13:24 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-25 02:13:24 (4259) [[32mINFO[0m] 
* 2023-10-25 02:13:24 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-25 02:13:24 (4229) [[32mINFO[0m] 
* 2023-10-25 02:13:54 (4242) [[32mINFO[0m] 
* 2023-10-25 02:13:54 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-25 02:13:54 (4259) [[32mINFO[0m] 
* 2023-10-25 02:13:54 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-25 02:13:54 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-25 02:14:18 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-25 02:14:18 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SoeYq33UAe/ea_profile.json
* 2023-10-25 02:14:20 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/SoeYq33UAe/ea_profile.json
* 2023-10-25 02:14:23 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-26 02:14:41 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-26 02:14:41 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-26 02:14:41 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-26 02:14:41 (4229) [[32mINFO[0m] 
* 2023-10-26 02:14:41 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-26 02:14:41 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-26 02:14:41 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-26 02:14:41 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-26 02:14:41 (4259) [[32mINFO[0m] 
* 2023-10-26 02:14:41 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-26 02:14:41 (4229) [[32mINFO[0m] 
* 2023-10-26 02:15:15 (4242) [[32mINFO[0m] 
* 2023-10-26 02:15:15 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-26 02:15:15 (4259) [[32mINFO[0m] 
* 2023-10-26 02:15:15 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-26 02:15:15 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-26 02:15:40 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-26 02:15:40 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/q_lfN4JKjL/ea_profile.json
* 2023-10-26 02:15:42 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/q_lfN4JKjL/ea_profile.json
* 2023-10-26 02:15:44 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-27 02:12:58 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-27 02:12:58 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-27 02:12:58 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-27 02:12:58 (4229) [[32mINFO[0m] 
* 2023-10-27 02:12:58 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-27 02:12:58 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-27 02:12:58 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-27 02:12:58 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-27 02:12:58 (4259) [[32mINFO[0m] 
* 2023-10-27 02:12:58 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-27 02:12:58 (4229) [[32mINFO[0m] 
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m] 
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m] 
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m] 
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m] 
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m] 
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m] 
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m] 
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]         or
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m] 
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]         compromise:
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m] 
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m] 
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-10-27 02:13:19 (4259) [[32mINFO[0m] 
* 2023-10-27 02:13:19 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-27 02:13:19 (1773) [[32mINFO[0m] Checking /scripts/sysup
* 2023-10-27 02:13:19 (4228) [[32mINFO[0m] Running: /scripts/sysup
* 2023-10-27 02:13:19 (4229) [[32mINFO[0m] 
* 2023-10-27 02:13:19 (4242) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-10-27 02:13:21 (4242) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-10-27 02:13:21 (4259) [[32mINFO[0m] 
* 2023-10-27 02:13:41 (1618) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-10-27 02:13:41 (1619) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-10-27 02:13:41 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-27 02:13:41 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-27 02:13:41 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6nFmgGFw8W/ea_profile.json
* 2023-10-27 02:13:44 (299) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6nFmgGFw8W/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-10-27 02:13:44 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-27 15:48:52 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-27 15:48:52 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-27 15:48:52 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-27 15:48:52 (4229) [[32mINFO[0m] 
* 2023-10-27 15:48:52 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-27 15:48:53 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-27 15:48:53 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-27 15:48:53 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-27 15:48:53 (4259) [[32mINFO[0m] 
* 2023-10-27 15:48:53 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-27 15:48:53 (4229) [[32mINFO[0m] 
* 2023-10-27 15:49:23 (4242) [[32mINFO[0m] 
* 2023-10-27 15:49:23 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-27 15:49:24 (4259) [[32mINFO[0m] 
* 2023-10-27 15:49:24 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-27 15:49:24 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-27 15:49:47 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-27 15:49:47 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nPhMvAaU0o/ea_profile.json
* 2023-10-27 15:49:48 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/nPhMvAaU0o/ea_profile.json
* 2023-10-27 15:49:50 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-28 02:14:05 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-28 02:14:05 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-28 02:14:05 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-28 02:14:05 (4229) [[32mINFO[0m] 
* 2023-10-28 02:14:05 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-28 02:14:05 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-28 02:14:05 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-28 02:14:05 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-28 02:14:05 (4259) [[32mINFO[0m] 
* 2023-10-28 02:14:05 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-28 02:14:05 (4229) [[32mINFO[0m] 
* 2023-10-28 02:14:37 (4242) [[32mINFO[0m] 
* 2023-10-28 02:14:37 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-28 02:14:37 (4259) [[32mINFO[0m] 
* 2023-10-28 02:14:37 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-28 02:14:37 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-28 02:15:02 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-28 02:15:02 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vuF2iVxYMH/ea_profile.json
* 2023-10-28 02:15:03 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/vuF2iVxYMH/ea_profile.json
* 2023-10-28 02:15:06 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-29 02:13:37 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-29 02:13:37 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-29 02:13:37 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-29 02:13:37 (4229) [[32mINFO[0m] 
* 2023-10-29 02:13:38 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-29 02:13:38 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-29 02:13:38 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-29 02:13:38 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-29 02:13:38 (4259) [[32mINFO[0m] 
* 2023-10-29 02:13:38 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-29 02:13:38 (4229) [[32mINFO[0m] 
* 2023-10-29 02:14:09 (4242) [[32mINFO[0m] 
* 2023-10-29 02:14:09 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-29 02:14:09 (4259) [[32mINFO[0m] 
* 2023-10-29 02:14:09 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-29 02:14:09 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-29 02:14:33 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-29 02:14:33 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NaNzgxLpVv/ea_profile.json
* 2023-10-29 02:14:35 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/NaNzgxLpVv/ea_profile.json
* 2023-10-29 02:14:37 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-30 02:13:02 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-30 02:13:02 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-30 02:13:02 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-30 02:13:02 (4229) [[32mINFO[0m] 
* 2023-10-30 02:13:02 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-30 02:13:03 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-30 02:13:03 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-30 02:13:03 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-30 02:13:03 (4259) [[32mINFO[0m] 
* 2023-10-30 02:13:03 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-30 02:13:03 (4229) [[32mINFO[0m] 
* 2023-10-30 02:13:33 (4242) [[32mINFO[0m] 
* 2023-10-30 02:13:33 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-30 02:13:33 (4259) [[32mINFO[0m] 
* 2023-10-30 02:13:33 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-30 02:13:33 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-30 02:13:56 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-30 02:13:56 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zDEmtxbV28/ea_profile.json
* 2023-10-30 02:13:58 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/zDEmtxbV28/ea_profile.json
* 2023-10-30 02:14:00 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-31 02:13:16 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-10-31 02:13:16 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-10-31 02:13:16 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-10-31 02:13:16 (4229) [[32mINFO[0m] 
* 2023-10-31 02:13:16 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-31 02:13:16 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-10-31 02:13:16 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-10-31 02:13:17 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-10-31 02:13:17 (4259) [[32mINFO[0m] 
* 2023-10-31 02:13:17 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-10-31 02:13:17 (4229) [[32mINFO[0m] 
* 2023-10-31 02:13:49 (4242) [[32mINFO[0m] 
* 2023-10-31 02:13:49 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-31 02:13:49 (4259) [[32mINFO[0m] 
* 2023-10-31 02:13:49 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-31 02:13:49 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-31 02:14:18 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-31 02:14:18 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/n0JO8x_Tfr/ea_profile.json
* 2023-10-31 02:14:20 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/n0JO8x_Tfr/ea_profile.json
* 2023-10-31 02:14:22 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-01 02:13:48 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-01 02:13:48 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-01 02:13:48 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-01 02:13:48 (4229) [[32mINFO[0m] 
* 2023-11-01 02:13:48 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-01 02:13:48 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-01 02:13:48 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-01 02:13:48 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-01 02:13:48 (4259) [[32mINFO[0m] 
* 2023-11-01 02:13:48 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-01 02:13:48 (4229) [[32mINFO[0m] 
* 2023-11-01 02:14:19 (4242) [[32mINFO[0m] 
* 2023-11-01 02:14:19 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-01 02:14:19 (4259) [[32mINFO[0m] 
* 2023-11-01 02:14:19 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-01 02:14:19 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-01 02:14:42 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-01 02:14:42 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/warOOP2QaF/ea_profile.json
* 2023-11-01 02:14:44 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/warOOP2QaF/ea_profile.json
* 2023-11-01 02:14:46 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-02 02:13:59 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-02 02:13:59 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-02 02:13:59 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-02 02:13:59 (4229) [[32mINFO[0m] 
* 2023-11-02 02:13:59 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-02 02:13:59 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-02 02:13:59 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-02 02:13:59 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-02 02:13:59 (4259) [[32mINFO[0m] 
* 2023-11-02 02:13:59 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-02 02:13:59 (4229) [[32mINFO[0m] 
* 2023-11-02 02:14:29 (4242) [[32mINFO[0m] 
* 2023-11-02 02:14:29 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-02 02:14:29 (4259) [[32mINFO[0m] 
* 2023-11-02 02:14:29 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-02 02:14:29 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-02 02:14:51 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-02 02:14:51 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EP4z0Bjk18/ea_profile.json
* 2023-11-02 02:14:52 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/EP4z0Bjk18/ea_profile.json
* 2023-11-02 02:14:55 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-03 02:13:39 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-03 02:13:39 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-03 02:13:39 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-03 02:13:39 (4229) [[32mINFO[0m] 
* 2023-11-03 02:13:39 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-03 02:13:40 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-03 02:13:40 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-03 02:13:40 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-03 02:13:40 (4259) [[32mINFO[0m] 
* 2023-11-03 02:13:40 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-03 02:13:40 (4229) [[32mINFO[0m] 
* 2023-11-03 02:14:10 (4242) [[32mINFO[0m] 
* 2023-11-03 02:14:10 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-03 02:14:10 (4259) [[32mINFO[0m] 
* 2023-11-03 02:14:10 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-03 02:14:10 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-03 02:14:33 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-03 02:14:33 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OGxnvAuEyv/ea_profile.json
* 2023-11-03 02:14:35 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/OGxnvAuEyv/ea_profile.json
* 2023-11-03 02:14:37 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-03 15:49:03 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-03 15:49:03 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-03 15:49:03 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-03 15:49:03 (4229) [[32mINFO[0m] 
* 2023-11-03 15:49:03 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-03 15:49:03 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-03 15:49:03 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-03 15:49:04 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-03 15:49:04 (4259) [[32mINFO[0m] 
* 2023-11-03 15:49:04 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-03 15:49:04 (4229) [[32mINFO[0m] 
* 2023-11-03 15:49:34 (4242) [[32mINFO[0m] 
* 2023-11-03 15:49:34 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-03 15:49:34 (4259) [[32mINFO[0m] 
* 2023-11-03 15:49:34 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-03 15:49:34 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-03 15:49:59 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-03 15:49:59 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KcpoQUzhr5/ea_profile.json
* 2023-11-03 15:50:00 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/KcpoQUzhr5/ea_profile.json
* 2023-11-03 15:50:02 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-04 02:13:45 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-04 02:13:45 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-04 02:13:45 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-04 02:13:45 (4229) [[32mINFO[0m] 
* 2023-11-04 02:13:46 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-04 02:13:46 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-04 02:13:46 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-04 02:13:46 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-04 02:13:46 (4259) [[32mINFO[0m] 
* 2023-11-04 02:13:46 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-04 02:13:46 (4229) [[32mINFO[0m] 
* 2023-11-04 02:14:16 (4242) [[32mINFO[0m] 
* 2023-11-04 02:14:16 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-04 02:14:17 (4259) [[32mINFO[0m] 
* 2023-11-04 02:14:17 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-04 02:14:17 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-04 02:14:40 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-04 02:14:40 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/A1eUyRcuvG/ea_profile.json
* 2023-11-04 02:14:42 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/A1eUyRcuvG/ea_profile.json
* 2023-11-04 02:14:45 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-05 02:13:59 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-05 02:13:59 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-05 02:13:59 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-05 02:13:59 (4229) [[32mINFO[0m] 
* 2023-11-05 02:13:59 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-05 02:14:00 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-05 02:14:00 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-05 02:14:00 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-05 02:14:00 (4259) [[32mINFO[0m] 
* 2023-11-05 02:14:00 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-05 02:14:00 (4229) [[32mINFO[0m] 
* 2023-11-05 02:14:32 (4242) [[32mINFO[0m] 
* 2023-11-05 02:14:32 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-05 02:14:32 (4259) [[32mINFO[0m] 
* 2023-11-05 02:14:32 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-05 02:14:32 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-05 02:14:55 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-05 02:14:55 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7VNAg4ve13/ea_profile.json
* 2023-11-05 02:14:57 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/7VNAg4ve13/ea_profile.json
* 2023-11-05 02:14:59 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-06 02:16:30 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-06 02:16:30 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-06 02:16:30 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-06 02:16:30 (4229) [[32mINFO[0m] 
* 2023-11-06 02:16:30 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-06 02:16:30 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-06 02:16:30 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-06 02:16:30 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-06 02:16:30 (4259) [[32mINFO[0m] 
* 2023-11-06 02:16:30 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-06 02:16:30 (4229) [[32mINFO[0m] 
* 2023-11-06 02:17:03 (4242) [[32mINFO[0m] 
* 2023-11-06 02:17:03 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-06 02:17:04 (4259) [[32mINFO[0m] 
* 2023-11-06 02:17:04 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-06 02:17:04 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-06 02:17:29 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-06 02:17:29 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xAud7zp0XW/ea_profile.json
* 2023-11-06 02:17:31 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/xAud7zp0XW/ea_profile.json
* 2023-11-06 02:17:33 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-07 02:13:15 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-07 02:13:15 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-07 02:13:15 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-07 02:13:15 (4229) [[32mINFO[0m] 
* 2023-11-07 02:13:15 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-07 02:13:16 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-07 02:13:16 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-07 02:13:16 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-07 02:13:16 (4259) [[32mINFO[0m] 
* 2023-11-07 02:13:16 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-07 02:13:16 (4229) [[32mINFO[0m] 
* 2023-11-07 02:13:48 (4242) [[32mINFO[0m] 
* 2023-11-07 02:13:48 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-07 02:13:48 (4259) [[32mINFO[0m] 
* 2023-11-07 02:13:48 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-07 02:13:48 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-07 02:14:11 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-07 02:14:11 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/C43muV7Lnh/ea_profile.json
* 2023-11-07 02:14:12 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/C43muV7Lnh/ea_profile.json
* 2023-11-07 02:14:15 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-08 02:13:18 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-08 02:13:18 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-08 02:13:18 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-08 02:13:18 (4229) [[32mINFO[0m] 
* 2023-11-08 02:13:18 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-08 02:13:19 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-08 02:13:19 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-08 02:13:19 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-08 02:13:19 (4259) [[32mINFO[0m] 
* 2023-11-08 02:13:19 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-08 02:13:19 (4229) [[32mINFO[0m] 
* 2023-11-08 02:13:31 (4242) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/e19c21a188ae6c799adf66778eadd8122f9d2b9e2444a638ae268e682c2df1a6-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-11-08 02:13:31 (4242) [[32mINFO[0m] Trying other mirror.
* 2023-11-08 02:13:31 (4242) [[32mINFO[0m] To address this issue please refer to the below wiki article 
* 2023-11-08 02:13:31 (4242) [[32mINFO[0m] 
* 2023-11-08 02:13:31 (4242) [[32mINFO[0m] https://wiki.centos.org/yum-errors
* 2023-11-08 02:13:31 (4242) [[32mINFO[0m] 
* 2023-11-08 02:13:31 (4242) [[32mINFO[0m] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2023-11-08 02:13:31 (4242) [[32mINFO[0m] 
* 2023-11-08 02:13:53 (4242) [[32mINFO[0m] 
* 2023-11-08 02:13:53 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-08 02:13:53 (4259) [[32mINFO[0m] 
* 2023-11-08 02:13:53 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-08 02:13:53 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-08 02:14:18 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-08 02:14:18 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5ERG05WsEt/ea_profile.json
* 2023-11-08 02:14:19 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/5ERG05WsEt/ea_profile.json
* 2023-11-08 02:14:22 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-09 02:15:21 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-09 02:15:21 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-09 02:15:21 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-09 02:15:21 (4229) [[32mINFO[0m] 
* 2023-11-09 02:15:21 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-09 02:15:21 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-09 02:15:21 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-09 02:15:22 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-09 02:15:22 (4259) [[32mINFO[0m] 
* 2023-11-09 02:15:22 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-09 02:15:22 (4229) [[32mINFO[0m] 
* 2023-11-09 02:15:53 (4242) [[32mINFO[0m] 
* 2023-11-09 02:15:53 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-09 02:15:53 (4259) [[32mINFO[0m] 
* 2023-11-09 02:15:53 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-09 02:15:53 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-09 02:16:21 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-09 02:16:21 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XcSKv8AmvR/ea_profile.json
* 2023-11-09 02:16:23 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/XcSKv8AmvR/ea_profile.json
* 2023-11-09 02:16:25 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-10 02:13:19 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-10 02:13:19 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-10 02:13:19 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-10 02:13:19 (4229) [[32mINFO[0m] 
* 2023-11-10 02:13:19 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-10 02:13:19 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-10 02:13:19 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-10 02:13:19 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-10 02:13:19 (4259) [[32mINFO[0m] 
* 2023-11-10 02:13:19 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-10 02:13:19 (4229) [[32mINFO[0m] 
* 2023-11-10 02:13:47 (4242) [[32mINFO[0m] 
* 2023-11-10 02:13:47 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-10 02:13:47 (4259) [[32mINFO[0m] 
* 2023-11-10 02:13:47 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-10 02:13:47 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-10 02:14:09 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-10 02:14:09 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gZ3RZYdOsR/ea_profile.json
* 2023-11-10 02:14:11 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/gZ3RZYdOsR/ea_profile.json
* 2023-11-10 02:14:14 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-10 15:47:31 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-10 15:47:31 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-10 15:47:31 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-10 15:47:31 (4229) [[32mINFO[0m] 
* 2023-11-10 15:47:32 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-10 15:47:32 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-10 15:47:32 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-10 15:47:32 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-10 15:47:32 (4259) [[32mINFO[0m] 
* 2023-11-10 15:47:32 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-10 15:47:32 (4229) [[32mINFO[0m] 
* 2023-11-10 15:48:07 (4242) [[32mINFO[0m] 
* 2023-11-10 15:48:07 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-10 15:48:07 (4259) [[32mINFO[0m] 
* 2023-11-10 15:48:07 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-10 15:48:07 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-10 15:48:30 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-10 15:48:30 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DYxl1SeQ1T/ea_profile.json
* 2023-11-10 15:48:32 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/DYxl1SeQ1T/ea_profile.json
* 2023-11-10 15:48:34 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-11 02:13:50 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-11 02:13:50 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-11 02:13:50 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-11 02:13:50 (4229) [[32mINFO[0m] 
* 2023-11-11 02:13:51 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-11 02:13:51 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-11 02:13:51 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-11 02:13:51 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-11 02:13:51 (4259) [[32mINFO[0m] 
* 2023-11-11 02:13:51 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-11 02:13:51 (4229) [[32mINFO[0m] 
* 2023-11-11 02:14:19 (4242) [[32mINFO[0m] 
* 2023-11-11 02:14:19 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-11 02:14:19 (4259) [[32mINFO[0m] 
* 2023-11-11 02:14:19 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-11 02:14:19 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-11 02:14:42 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-11 02:14:42 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/41DFW4JjNT/ea_profile.json
* 2023-11-11 02:14:44 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/41DFW4JjNT/ea_profile.json
* 2023-11-11 02:14:46 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-12 02:13:44 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-12 02:13:44 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-12 02:13:44 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-12 02:13:44 (4229) [[32mINFO[0m] 
* 2023-11-12 02:13:44 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-12 02:13:44 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-12 02:13:44 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-12 02:13:44 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-12 02:13:44 (4259) [[32mINFO[0m] 
* 2023-11-12 02:13:44 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-12 02:13:44 (4229) [[32mINFO[0m] 
* 2023-11-12 02:14:14 (4242) [[32mINFO[0m] 
* 2023-11-12 02:14:14 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-12 02:14:14 (4259) [[32mINFO[0m] 
* 2023-11-12 02:14:14 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-12 02:14:14 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-12 02:14:53 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-12 02:14:53 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5rlogd2cKp/ea_profile.json
* 2023-11-12 02:14:55 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/5rlogd2cKp/ea_profile.json
* 2023-11-12 02:14:56 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-13 02:13:13 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-13 02:13:13 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-13 02:13:13 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-13 02:13:13 (4229) [[32mINFO[0m] 
* 2023-11-13 02:13:14 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-13 02:13:14 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-13 02:13:14 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-13 02:13:14 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-13 02:13:14 (4259) [[32mINFO[0m] 
* 2023-11-13 02:13:14 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-13 02:13:14 (4229) [[32mINFO[0m] 
* 2023-11-13 02:13:46 (4242) [[32mINFO[0m] 
* 2023-11-13 02:13:46 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-13 02:13:47 (4259) [[32mINFO[0m] 
* 2023-11-13 02:13:47 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-13 02:13:47 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-13 02:14:09 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-13 02:14:09 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aBC_rjm1u_/ea_profile.json
* 2023-11-13 02:14:10 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/aBC_rjm1u_/ea_profile.json
* 2023-11-13 02:14:13 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-14 02:25:52 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-14 02:25:52 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-14 02:25:52 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-14 02:25:52 (4229) [[32mINFO[0m] 
* 2023-11-14 02:25:52 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-14 02:25:53 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-14 02:25:53 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-14 02:25:53 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-14 02:25:53 (4259) [[32mINFO[0m] 
* 2023-11-14 02:25:53 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-14 02:25:53 (4229) [[32mINFO[0m] 
* 2023-11-14 02:26:16 (4242) [[32mINFO[0m] https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
* 2023-11-14 02:26:16 (4242) [[32mINFO[0m] Trying other mirror.
* 2023-11-14 02:27:17 (4242) [[32mINFO[0m] https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/0705bd4164b91c9c061b2b6f9f7e7dd21c224cfde48458a627229006ecb69e17-updateinfo.xml.gz: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/0705bd4164b91c9c061b2b6f9f7e7dd21c224cfde48458a627229006ecb69e17-updateinfo.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-11-14 02:27:17 (4242) [[32mINFO[0m] Trying other mirror.
* 2023-11-14 02:27:34 (4242) [[32mINFO[0m] 
* 2023-11-14 02:27:34 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-14 02:27:34 (4259) [[32mINFO[0m] 
* 2023-11-14 02:27:34 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-14 02:27:34 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-14 02:31:03 (1618) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-11-14 02:31:03 (1619) [[31mERROR[0m] https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
https://archive.mariadb.org/mariadb-10.5/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.5/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.5/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
* 2023-11-14 02:31:03 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-14 02:31:03 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-14 02:31:03 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bC8fG1nPJe/ea_profile.json
* 2023-11-14 02:31:05 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/bC8fG1nPJe/ea_profile.json
* 2023-11-14 02:31:07 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-15 02:13:21 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-15 02:13:21 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-15 02:13:21 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-15 02:13:21 (4229) [[32mINFO[0m] 
* 2023-11-15 02:13:21 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-15 02:13:22 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-15 02:13:22 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-15 02:13:22 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-15 02:13:22 (4259) [[32mINFO[0m] 
* 2023-11-15 02:13:22 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-15 02:13:22 (4229) [[32mINFO[0m] 
* 2023-11-15 02:13:33 (4242) [[32mINFO[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/d065bd8885289871369c1468a8bbcbc91eabd571c588d6d6ed23f5f1f286626f-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
* 2023-11-15 02:13:33 (4242) [[32mINFO[0m] Trying other mirror.
* 2023-11-15 02:13:33 (4242) [[32mINFO[0m] To address this issue please refer to the below wiki article 
* 2023-11-15 02:13:33 (4242) [[32mINFO[0m] 
* 2023-11-15 02:13:33 (4242) [[32mINFO[0m] https://wiki.centos.org/yum-errors
* 2023-11-15 02:13:33 (4242) [[32mINFO[0m] 
* 2023-11-15 02:13:33 (4242) [[32mINFO[0m] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2023-11-15 02:13:33 (4242) [[32mINFO[0m] 
* 2023-11-15 02:13:51 (4242) [[32mINFO[0m] 
* 2023-11-15 02:13:51 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-15 02:13:51 (4259) [[32mINFO[0m] 
* 2023-11-15 02:13:51 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-15 02:13:51 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-15 02:14:15 (1618) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-11-15 02:14:15 (1619) [[31mERROR[0m] http://mirrors.bfsu.edu.cn/epel/7/x86_64/repodata/41235f8a2b3e9ffb86d5626886711d4e0f1d1c0ac20d3d902cefc07d61e18ff5-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-11-15 02:14:15 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-15 02:14:15 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-15 02:14:15 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vhQ4BnYwKD/ea_profile.json
* 2023-11-15 02:14:17 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/vhQ4BnYwKD/ea_profile.json
* 2023-11-15 02:14:19 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-16 02:14:57 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-16 02:14:57 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-16 02:14:57 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-16 02:14:57 (4229) [[32mINFO[0m] 
* 2023-11-16 02:14:57 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-16 02:14:57 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-16 02:14:57 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-16 02:14:58 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-16 02:14:58 (4259) [[32mINFO[0m] 
* 2023-11-16 02:14:58 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-16 02:14:58 (4229) [[32mINFO[0m] 
* 2023-11-16 02:15:30 (4242) [[32mINFO[0m] 
* 2023-11-16 02:15:30 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-16 02:15:30 (4259) [[32mINFO[0m] 
* 2023-11-16 02:15:30 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-16 02:15:30 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-16 02:16:00 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-16 02:16:01 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/CbhhXGwZdf/ea_profile.json
* 2023-11-16 02:16:02 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/CbhhXGwZdf/ea_profile.json
* 2023-11-16 02:16:05 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-17 02:13:24 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-17 02:13:24 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-17 02:13:24 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-17 02:13:24 (4229) [[32mINFO[0m] 
* 2023-11-17 02:13:24 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-17 02:13:24 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-17 02:13:24 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-17 02:13:25 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-17 02:13:25 (4259) [[32mINFO[0m] 
* 2023-11-17 02:13:25 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-17 02:13:25 (4229) [[32mINFO[0m] 
* 2023-11-17 02:13:56 (4242) [[32mINFO[0m] 
* 2023-11-17 02:13:56 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-17 02:13:57 (4259) [[32mINFO[0m] 
* 2023-11-17 02:13:57 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-17 02:13:57 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-17 02:14:21 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-17 02:14:21 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/J6qpI6QyZm/ea_profile.json
* 2023-11-17 02:14:22 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/J6qpI6QyZm/ea_profile.json
* 2023-11-17 02:14:25 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-17 15:47:27 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-17 15:47:27 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-17 15:47:27 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-17 15:47:27 (4229) [[32mINFO[0m] 
* 2023-11-17 15:47:27 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-17 15:47:27 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-17 15:47:27 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-17 15:47:27 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-17 15:47:27 (4259) [[32mINFO[0m] 
* 2023-11-17 15:47:27 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-17 15:47:27 (4229) [[32mINFO[0m] 
* 2023-11-17 15:48:01 (4242) [[32mINFO[0m] 
* 2023-11-17 15:48:01 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-17 15:48:01 (4259) [[32mINFO[0m] 
* 2023-11-17 15:48:01 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-17 15:48:01 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-17 15:48:28 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-17 15:48:28 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/kBdApCdEdD/ea_profile.json
* 2023-11-17 15:48:29 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/kBdApCdEdD/ea_profile.json
* 2023-11-17 15:48:31 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-18 02:13:45 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-18 02:13:45 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-18 02:13:45 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-18 02:13:45 (4229) [[32mINFO[0m] 
* 2023-11-18 02:13:45 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-18 02:13:45 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-18 02:13:45 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-18 02:13:46 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-18 02:13:46 (4259) [[32mINFO[0m] 
* 2023-11-18 02:13:46 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-18 02:13:46 (4229) [[32mINFO[0m] 
* 2023-11-18 02:14:18 (4242) [[32mINFO[0m] 
* 2023-11-18 02:14:18 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-18 02:14:18 (4259) [[32mINFO[0m] 
* 2023-11-18 02:14:18 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-18 02:14:18 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-18 02:14:43 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-18 02:14:43 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6Q0Uw8oMfN/ea_profile.json
* 2023-11-18 02:14:45 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/6Q0Uw8oMfN/ea_profile.json
* 2023-11-18 02:14:47 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-19 02:13:54 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-19 02:13:54 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-19 02:13:54 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-19 02:13:54 (4229) [[32mINFO[0m] 
* 2023-11-19 02:13:55 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-19 02:13:55 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-19 02:13:55 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-19 02:13:55 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-19 02:13:55 (4259) [[32mINFO[0m] 
* 2023-11-19 02:13:55 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-19 02:13:55 (4229) [[32mINFO[0m] 
* 2023-11-19 02:14:27 (4242) [[32mINFO[0m] 
* 2023-11-19 02:14:27 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-19 02:14:27 (4259) [[32mINFO[0m] 
* 2023-11-19 02:14:27 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-19 02:14:27 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-19 02:14:52 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-19 02:14:52 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nx0iYiuY97/ea_profile.json
* 2023-11-19 02:14:54 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/nx0iYiuY97/ea_profile.json
* 2023-11-19 02:14:57 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-20 02:13:23 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-20 02:13:23 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-20 02:13:23 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-20 02:13:23 (4229) [[32mINFO[0m] 
* 2023-11-20 02:13:23 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-20 02:13:23 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-20 02:13:23 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-20 02:13:24 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-20 02:13:24 (4259) [[32mINFO[0m] 
* 2023-11-20 02:13:24 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-20 02:13:24 (4229) [[32mINFO[0m] 
* 2023-11-20 02:13:54 (4242) [[32mINFO[0m] 
* 2023-11-20 02:13:54 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-20 02:13:54 (4259) [[32mINFO[0m] 
* 2023-11-20 02:13:54 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-20 02:13:54 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-20 02:14:19 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-20 02:14:19 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pTVgQJ0SjE/ea_profile.json
* 2023-11-20 02:14:21 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/pTVgQJ0SjE/ea_profile.json
* 2023-11-20 02:14:25 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-21 02:13:16 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-21 02:13:16 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-21 02:13:16 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-21 02:13:16 (4229) [[32mINFO[0m] 
* 2023-11-21 02:13:17 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-21 02:13:17 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-21 02:13:17 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-21 02:13:17 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-21 02:13:17 (4259) [[32mINFO[0m] 
* 2023-11-21 02:13:17 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-21 02:13:17 (4229) [[32mINFO[0m] 
* 2023-11-21 02:13:51 (4242) [[32mINFO[0m] 
* 2023-11-21 02:13:51 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-21 02:13:51 (4259) [[32mINFO[0m] 
* 2023-11-21 02:13:51 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-21 02:13:51 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-21 02:14:17 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-21 02:14:17 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zz7TKiAkrG/ea_profile.json
* 2023-11-21 02:14:19 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/zz7TKiAkrG/ea_profile.json
* 2023-11-21 02:14:23 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-22 02:13:19 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-22 02:13:19 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-22 02:13:19 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-22 02:13:19 (4229) [[32mINFO[0m] 
* 2023-11-22 02:13:19 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-22 02:13:19 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-22 02:13:19 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-22 02:13:19 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-22 02:13:19 (4259) [[32mINFO[0m] 
* 2023-11-22 02:13:19 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-22 02:13:19 (4229) [[32mINFO[0m] 
* 2023-11-22 02:13:51 (4242) [[32mINFO[0m] 
* 2023-11-22 02:13:51 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-22 02:13:52 (4259) [[32mINFO[0m] 
* 2023-11-22 02:13:52 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-22 02:13:52 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-22 02:14:17 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-22 02:14:17 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aPePHiTTqD/ea_profile.json
* 2023-11-22 02:14:19 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/aPePHiTTqD/ea_profile.json
* 2023-11-22 02:14:22 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-23 02:13:42 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-23 02:13:42 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-23 02:13:42 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-23 02:13:42 (4229) [[32mINFO[0m] 
* 2023-11-23 02:13:43 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-23 02:13:43 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-23 02:13:43 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-23 02:13:43 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-23 02:13:43 (4259) [[32mINFO[0m] 
* 2023-11-23 02:13:43 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-23 02:13:43 (4229) [[32mINFO[0m] 
* 2023-11-23 02:14:16 (4242) [[32mINFO[0m] 
* 2023-11-23 02:14:16 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-23 02:14:17 (4259) [[32mINFO[0m] 
* 2023-11-23 02:14:17 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-23 02:14:17 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-23 02:14:41 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-23 02:14:41 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cViAAUoYBB/ea_profile.json
* 2023-11-23 02:14:43 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/cViAAUoYBB/ea_profile.json
* 2023-11-23 02:14:47 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-24 02:14:23 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-24 02:14:23 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-24 02:14:23 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-24 02:14:23 (4229) [[32mINFO[0m] 
* 2023-11-24 02:14:24 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-24 02:14:24 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-24 02:14:24 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-24 02:14:24 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-24 02:14:24 (4259) [[32mINFO[0m] 
* 2023-11-24 02:14:24 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-24 02:14:24 (4229) [[32mINFO[0m] 
* 2023-11-24 02:14:56 (4242) [[32mINFO[0m] 
* 2023-11-24 02:14:56 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-24 02:14:56 (4259) [[32mINFO[0m] 
* 2023-11-24 02:14:56 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-24 02:14:56 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-24 02:15:22 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-24 02:15:22 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5abWjb3Q2J/ea_profile.json
* 2023-11-24 02:15:24 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/5abWjb3Q2J/ea_profile.json
* 2023-11-24 02:15:28 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-24 15:47:22 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-24 15:47:22 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-24 15:47:22 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-24 15:47:22 (4229) [[32mINFO[0m] 
* 2023-11-24 15:47:22 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-24 15:47:22 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-24 15:47:22 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-24 15:47:22 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-24 15:47:22 (4259) [[32mINFO[0m] 
* 2023-11-24 15:47:22 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-24 15:47:22 (4229) [[32mINFO[0m] 
* 2023-11-24 15:47:54 (4242) [[32mINFO[0m] 
* 2023-11-24 15:47:54 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-24 15:47:54 (4259) [[32mINFO[0m] 
* 2023-11-24 15:47:54 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-24 15:47:54 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-24 15:48:22 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-24 15:48:22 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nixhR3QB2V/ea_profile.json
* 2023-11-24 15:48:23 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/nixhR3QB2V/ea_profile.json
* 2023-11-24 15:48:27 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-25 02:13:58 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-25 02:13:58 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-25 02:13:58 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-25 02:13:58 (4229) [[32mINFO[0m] 
* 2023-11-25 02:13:58 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-25 02:13:58 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-25 02:13:58 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-25 02:13:58 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-25 02:13:58 (4259) [[32mINFO[0m] 
* 2023-11-25 02:13:58 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-25 02:13:58 (4229) [[32mINFO[0m] 
* 2023-11-25 02:14:32 (4242) [[32mINFO[0m] 
* 2023-11-25 02:14:32 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-25 02:14:32 (4259) [[32mINFO[0m] 
* 2023-11-25 02:14:32 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-25 02:14:32 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-25 02:14:57 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-25 02:14:57 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uIam262LYb/ea_profile.json
* 2023-11-25 02:14:59 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/uIam262LYb/ea_profile.json
* 2023-11-25 02:15:02 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-26 02:14:33 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-26 02:14:33 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-26 02:14:33 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-26 02:14:33 (4229) [[32mINFO[0m] 
* 2023-11-26 02:14:33 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-26 02:14:33 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-26 02:14:33 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-26 02:14:33 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-26 02:14:33 (4259) [[32mINFO[0m] 
* 2023-11-26 02:14:33 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-26 02:14:33 (4229) [[32mINFO[0m] 
* 2023-11-26 02:15:04 (4242) [[32mINFO[0m] 
* 2023-11-26 02:15:04 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-26 02:15:04 (4259) [[32mINFO[0m] 
* 2023-11-26 02:15:04 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-26 02:15:04 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-26 02:15:28 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-26 02:15:28 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4dsI8Z5_l5/ea_profile.json
* 2023-11-26 02:15:30 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/4dsI8Z5_l5/ea_profile.json
* 2023-11-26 02:15:33 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-27 02:13:20 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-27 02:13:20 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-27 02:13:20 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-27 02:13:20 (4229) [[32mINFO[0m] 
* 2023-11-27 02:13:20 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-27 02:13:20 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-27 02:13:20 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-27 02:13:20 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-27 02:13:20 (4259) [[32mINFO[0m] 
* 2023-11-27 02:13:20 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-27 02:13:20 (4229) [[32mINFO[0m] 
* 2023-11-27 02:13:50 (4242) [[32mINFO[0m] 
* 2023-11-27 02:13:50 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-27 02:13:50 (4259) [[32mINFO[0m] 
* 2023-11-27 02:13:50 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-27 02:13:50 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-27 02:14:16 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-27 02:14:16 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/t2q5t371lJ/ea_profile.json
* 2023-11-27 02:14:18 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/t2q5t371lJ/ea_profile.json
* 2023-11-27 02:14:21 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-28 02:13:25 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-28 02:13:25 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-28 02:13:25 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-28 02:13:25 (4229) [[32mINFO[0m] 
* 2023-11-28 02:13:25 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-28 02:13:26 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-28 02:13:26 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-28 02:13:26 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-28 02:13:26 (4259) [[32mINFO[0m] 
* 2023-11-28 02:13:26 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-28 02:13:26 (4229) [[32mINFO[0m] 
* 2023-11-28 02:13:59 (4242) [[32mINFO[0m] 
* 2023-11-28 02:13:59 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-28 02:13:59 (4259) [[32mINFO[0m] 
* 2023-11-28 02:13:59 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-28 02:13:59 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-28 02:14:26 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-28 02:14:26 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yrwDwgzyAz/ea_profile.json
* 2023-11-28 02:14:28 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/yrwDwgzyAz/ea_profile.json
* 2023-11-28 02:14:31 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-29 02:13:16 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-29 02:13:16 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-29 02:13:16 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-29 02:13:16 (4229) [[32mINFO[0m] 
* 2023-11-29 02:13:16 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-29 02:13:17 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-29 02:13:17 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-29 02:13:17 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-29 02:13:17 (4259) [[32mINFO[0m] 
* 2023-11-29 02:13:17 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-29 02:13:17 (4229) [[32mINFO[0m] 
* 2023-11-29 02:13:51 (4242) [[32mINFO[0m] 
* 2023-11-29 02:13:51 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-29 02:13:51 (4259) [[32mINFO[0m] 
* 2023-11-29 02:13:51 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-29 02:13:51 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-29 02:14:17 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-29 02:14:17 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NOp1t6UnIK/ea_profile.json
* 2023-11-29 02:14:18 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/NOp1t6UnIK/ea_profile.json
* 2023-11-29 02:14:21 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-30 02:13:22 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-11-30 02:13:22 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-11-30 02:13:22 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-11-30 02:13:22 (4229) [[32mINFO[0m] 
* 2023-11-30 02:13:22 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-30 02:13:22 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-11-30 02:13:22 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-11-30 02:13:22 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-11-30 02:13:22 (4259) [[32mINFO[0m] 
* 2023-11-30 02:13:22 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-11-30 02:13:22 (4229) [[32mINFO[0m] 
* 2023-11-30 02:13:57 (4242) [[32mINFO[0m] 
* 2023-11-30 02:13:57 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-30 02:13:57 (4259) [[32mINFO[0m] 
* 2023-11-30 02:13:57 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-30 02:13:57 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-30 02:14:21 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-30 02:14:24 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TOrY2V4rAX/ea_profile.json
* 2023-11-30 02:14:26 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/TOrY2V4rAX/ea_profile.json
* 2023-11-30 02:14:30 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-01 02:16:05 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-01 02:16:05 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-01 02:16:05 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-01 02:16:05 (4229) [[32mINFO[0m] 
* 2023-12-01 02:16:06 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-01 02:16:06 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-01 02:16:06 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-12-01 02:16:06 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-01 02:16:06 (4259) [[32mINFO[0m] 
* 2023-12-01 02:16:06 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-01 02:16:06 (4229) [[32mINFO[0m] 
* 2023-12-01 02:16:36 (4242) [[32mINFO[0m] 
* 2023-12-01 02:16:36 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-01 02:16:36 (4259) [[32mINFO[0m] 
* 2023-12-01 02:16:36 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-01 02:16:36 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-01 02:17:10 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-01 02:17:10 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xWwm3Iuho6/ea_profile.json
* 2023-12-01 02:17:12 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/xWwm3Iuho6/ea_profile.json
* 2023-12-01 02:17:16 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-01 15:48:03 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-01 15:48:03 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-01 15:48:03 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-01 15:48:03 (4229) [[32mINFO[0m] 
* 2023-12-01 15:48:03 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-01 15:48:03 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-01 15:48:03 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-12-01 15:48:04 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-01 15:48:04 (4259) [[32mINFO[0m] 
* 2023-12-01 15:48:04 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-01 15:48:04 (4229) [[32mINFO[0m] 
* 2023-12-01 15:48:34 (4242) [[32mINFO[0m] 
* 2023-12-01 15:48:34 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-01 15:48:34 (4259) [[32mINFO[0m] 
* 2023-12-01 15:48:34 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-01 15:48:34 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-01 15:49:00 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-01 15:49:00 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QOzqfqbLyf/ea_profile.json
* 2023-12-01 15:49:02 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/QOzqfqbLyf/ea_profile.json
* 2023-12-01 15:49:06 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-02 02:13:57 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-02 02:13:57 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-02 02:13:57 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-02 02:13:57 (4229) [[32mINFO[0m] 
* 2023-12-02 02:13:57 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-02 02:13:57 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-02 02:13:57 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-12-02 02:13:57 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-02 02:13:57 (4259) [[32mINFO[0m] 
* 2023-12-02 02:13:57 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-02 02:13:57 (4229) [[32mINFO[0m] 
* 2023-12-02 02:14:28 (4242) [[32mINFO[0m] 
* 2023-12-02 02:14:28 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-02 02:14:28 (4259) [[32mINFO[0m] 
* 2023-12-02 02:14:28 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-02 02:14:28 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-02 02:14:53 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-02 02:14:53 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZWGgjcLStL/ea_profile.json
* 2023-12-02 02:14:55 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/ZWGgjcLStL/ea_profile.json
* 2023-12-02 02:14:58 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-03 02:13:54 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-03 02:13:54 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-03 02:13:54 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-03 02:13:54 (4229) [[32mINFO[0m] 
* 2023-12-03 02:13:54 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-03 02:13:55 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-03 02:13:55 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-12-03 02:13:55 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-03 02:13:55 (4259) [[32mINFO[0m] 
* 2023-12-03 02:13:55 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-03 02:13:55 (4229) [[32mINFO[0m] 
* 2023-12-03 02:14:25 (4242) [[32mINFO[0m] 
* 2023-12-03 02:14:25 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-03 02:14:25 (4259) [[32mINFO[0m] 
* 2023-12-03 02:14:25 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-03 02:14:25 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-03 02:14:51 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-03 02:14:51 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jUNQmHua5X/ea_profile.json
* 2023-12-03 02:14:53 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/jUNQmHua5X/ea_profile.json
* 2023-12-03 02:14:56 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-04 02:13:27 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-04 02:13:27 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-04 02:13:27 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-04 02:13:27 (4229) [[32mINFO[0m] 
* 2023-12-04 02:13:27 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-04 02:13:27 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-04 02:13:27 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-12-04 02:13:29 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-04 02:13:29 (4259) [[32mINFO[0m] 
* 2023-12-04 02:13:29 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-04 02:13:29 (4229) [[32mINFO[0m] 
* 2023-12-04 02:14:04 (4242) [[32mINFO[0m] 
* 2023-12-04 02:14:04 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-04 02:14:04 (4259) [[32mINFO[0m] 
* 2023-12-04 02:14:04 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-04 02:14:04 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-04 02:14:31 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-04 02:14:31 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LfP5SJfzyv/ea_profile.json
* 2023-12-04 02:14:32 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/LfP5SJfzyv/ea_profile.json
* 2023-12-04 02:14:36 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-05 02:13:19 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: Failed to download signature at URL 'http://repo-ir.amazeservice.net/cpanelsync/TIERS.json.asc'.
* 2023-12-05 02:13:19 (299) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 1940.
* 2023-12-05 02:13:19 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-06 02:13:52 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-06 02:13:52 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-06 02:13:52 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-06 02:13:52 (4229) [[32mINFO[0m] 
* 2023-12-06 02:13:52 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-06 02:13:52 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-06 02:13:52 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-12-06 02:13:52 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-06 02:13:52 (4259) [[32mINFO[0m] 
* 2023-12-06 02:13:52 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-06 02:13:52 (4229) [[32mINFO[0m] 
* 2023-12-06 02:14:27 (4242) [[32mINFO[0m] 
* 2023-12-06 02:14:27 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-06 02:14:27 (4259) [[32mINFO[0m] 
* 2023-12-06 02:14:27 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-06 02:14:27 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-06 02:14:52 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-06 02:14:52 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RFYdM9AKS8/ea_profile.json
* 2023-12-06 02:14:53 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/RFYdM9AKS8/ea_profile.json
* 2023-12-06 02:14:57 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-07 02:13:22 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-07 02:13:22 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-07 02:13:22 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-07 02:13:22 (4229) [[32mINFO[0m] 
* 2023-12-07 02:13:22 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-07 02:13:22 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-07 02:13:22 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-12-07 02:13:22 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-07 02:13:22 (4259) [[32mINFO[0m] 
* 2023-12-07 02:13:22 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-07 02:13:22 (4229) [[32mINFO[0m] 
* 2023-12-07 02:13:56 (4242) [[32mINFO[0m] 
* 2023-12-07 02:13:56 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-07 02:13:57 (4259) [[32mINFO[0m] 
* 2023-12-07 02:13:57 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-07 02:13:57 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-07 02:14:26 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-07 02:14:26 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/kkzAImeqE4/ea_profile.json
* 2023-12-07 02:14:27 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/kkzAImeqE4/ea_profile.json
* 2023-12-07 02:14:31 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-08 02:20:38 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-08 02:20:38 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-08 02:20:38 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-08 02:20:38 (4229) [[32mINFO[0m] 
* 2023-12-08 02:20:38 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-08 02:20:38 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-08 02:20:38 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-12-08 02:20:39 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-08 02:20:39 (4259) [[32mINFO[0m] 
* 2023-12-08 02:20:39 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-08 02:20:39 (4229) [[32mINFO[0m] 
* 2023-12-08 02:21:11 (4242) [[32mINFO[0m] 
* 2023-12-08 02:21:11 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-08 02:21:11 (4259) [[32mINFO[0m] 
* 2023-12-08 02:21:11 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-08 02:21:11 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-08 02:21:35 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-08 02:21:35 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qYAr5pelMV/ea_profile.json
* 2023-12-08 02:21:37 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/qYAr5pelMV/ea_profile.json
* 2023-12-08 02:21:40 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-08 15:48:41 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-08 15:48:41 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-08 15:48:41 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-08 15:48:41 (4229) [[32mINFO[0m] 
* 2023-12-08 15:48:41 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-08 15:48:41 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-08 15:48:41 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-12-08 15:48:41 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-08 15:48:41 (4259) [[32mINFO[0m] 
* 2023-12-08 15:48:41 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-08 15:48:41 (4229) [[32mINFO[0m] 
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m] 
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m] 
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m] 
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m] 
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m] 
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m] 
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m] 
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]         or
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m] 
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]         compromise:
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m] 
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m] 
* 2023-12-08 15:48:46 (4242) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-08 15:48:46 (4259) [[32mINFO[0m] 
* 2023-12-08 15:48:46 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-08 15:48:46 (1773) [[32mINFO[0m] Checking /scripts/sysup
* 2023-12-08 15:48:46 (4228) [[32mINFO[0m] Running: /scripts/sysup
* 2023-12-08 15:48:46 (4229) [[32mINFO[0m] 
* 2023-12-08 15:48:47 (4242) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-08 15:48:48 (4242) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-12-08 15:48:48 (4259) [[32mINFO[0m] 
* 2023-12-08 15:48:50 (1618) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-12-08 15:48:50 (1619) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-08 15:48:50 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-08 15:48:51 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-08 15:48:51 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Kol3E_jN7R/ea_profile.json
* 2023-12-08 15:48:56 (299) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Kol3E_jN7R/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-12-08 15:48:56 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-09 02:13:53 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-09 02:13:53 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-09 02:13:53 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-09 02:13:53 (4229) [[32mINFO[0m] 
* 2023-12-09 02:13:53 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-09 02:13:53 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-09 02:13:53 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-12-09 02:13:53 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-09 02:13:53 (4259) [[32mINFO[0m] 
* 2023-12-09 02:13:53 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-09 02:13:53 (4229) [[32mINFO[0m] 
* 2023-12-09 02:14:24 (4242) [[32mINFO[0m] 
* 2023-12-09 02:14:24 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-09 02:14:24 (4259) [[32mINFO[0m] 
* 2023-12-09 02:14:24 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-09 02:14:25 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-09 02:14:48 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-09 02:14:48 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UFSoOVfdpX/ea_profile.json
* 2023-12-09 02:14:49 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/UFSoOVfdpX/ea_profile.json
* 2023-12-09 02:14:53 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-10 02:13:47 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-10 02:13:47 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-10 02:13:47 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-10 02:13:47 (4229) [[32mINFO[0m] 
* 2023-12-10 02:13:47 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-10 02:13:48 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-10 02:13:48 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-12-10 02:13:48 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-10 02:13:48 (4259) [[32mINFO[0m] 
* 2023-12-10 02:13:48 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-10 02:13:48 (4229) [[32mINFO[0m] 
* 2023-12-10 02:14:16 (4242) [[32mINFO[0m] 
* 2023-12-10 02:14:16 (4242) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-10 02:14:17 (4259) [[32mINFO[0m] 
* 2023-12-10 02:14:17 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-10 02:14:17 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-10 02:14:40 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-10 02:14:40 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cR3ktje52Q/ea_profile.json
* 2023-12-10 02:14:42 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/cR3ktje52Q/ea_profile.json
* 2023-12-10 02:14:46 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-10 18:17:52 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-10 18:17:52 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-10 18:17:52 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-10 18:17:52 (4229) [[32mINFO[0m] 
* 2023-12-10 18:17:52 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-10 18:17:53 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-10 18:17:53 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-12-10 18:17:53 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-10 18:17:53 (4259) [[32mINFO[0m] 
* 2023-12-10 18:17:53 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-10 18:17:53 (4229) [[32mINFO[0m] 
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m] 
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m] 
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m] 
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m] 
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m] 
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m] 
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m] 
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]         or
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m] 
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]         compromise:
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m] 
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m] 
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-10 18:17:57 (4259) [[32mINFO[0m] 
* 2023-12-10 18:17:57 (1759) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-10 18:17:57 (1773) [[32mINFO[0m] Checking /scripts/sysup
* 2023-12-10 18:17:57 (4228) [[32mINFO[0m] Running: /scripts/sysup
* 2023-12-10 18:17:57 (4229) [[32mINFO[0m] 
* 2023-12-10 18:17:57 (4242) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-10 18:17:59 (4242) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-12-10 18:17:59 (4259) [[32mINFO[0m] 
* 2023-12-10 18:18:06 (1618) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-12-10 18:18:06 (1619) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-10 18:18:06 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-10 18:18:07 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-10 18:18:07 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uWMobOPStL/ea_profile.json
* 2023-12-10 18:18:13 (299) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uWMobOPStL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-12-10 18:18:13 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-11 02:13:22 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-11 02:13:22 (1752) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-11 02:13:22 (4228) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-11 02:13:22 (4229) [[32mINFO[0m] 
* 2023-12-11 02:13:22 (4242) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-11 02:13:22 (4242) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-11 02:13:22 (4242) [[32mINFO[0m]               : epel extras updates
* 2023-12-11 02:13:23 (4242) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-11 02:13:23 (4259) [[32mINFO[0m] 
* 2023-12-11 02:13:23 (4228) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-11 02:13:23 (4229) [[32mINFO[0m] 
* 2023-12-11 02:13:55 (4259) [[32mINFO[0m] 
* 2023-12-11 02:13:55 (1773) [[32mINFO[0m] Checking /scripts/sysup
* 2023-12-11 02:13:55 (4228) [[32mINFO[0m] Running: /scripts/sysup
* 2023-12-11 02:13:55 (4229) [[32mINFO[0m] 
* 2023-12-11 02:13:55 (4242) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-11 02:13:56 (4242) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-12-11 02:13:56 (4259) [[32mINFO[0m] 
* 2023-12-11 02:14:24 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-11 02:14:24 (2270) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5ov9EOI5zc/ea_profile.json
* 2023-12-11 02:14:26 (2293) [[32mINFO[0m] Backed up EA4 profile to /tmp/5ov9EOI5zc/ea_profile.json
* 2023-12-11 02:14:28 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.90.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.102.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-12-11 02:14:29 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-12 02:13:20 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: Signature verification failed for URL 'http://repo-ir.amazeservice.net/cpanelsync/TIERS.json'. Signature rollback detected. Please see https://go.cpanel.net/sigerrors for further information about this error.
* 2023-12-12 02:13:20 (299) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 1941.
* 2023-12-12 02:13:20 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-13 02:13:25 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: Signature verification failed for URL 'http://repo-ir.amazeservice.net/cpanelsync/TIERS.json'. Signature rollback detected. Please see https://go.cpanel.net/sigerrors for further information about this error.
* 2023-12-13 02:13:25 (299) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 1941.
* 2023-12-13 02:13:25 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-14 02:21:02 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-14 02:21:02 (1753) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-14 02:21:02 (4229) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-14 02:21:02 (4230) [[32mINFO[0m] 
* 2023-12-14 02:21:02 (4243) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-14 02:21:02 (4243) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-14 02:21:02 (4243) [[32mINFO[0m]               : epel extras updates
* 2023-12-14 02:21:02 (4243) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-14 02:21:02 (4260) [[32mINFO[0m] 
* 2023-12-14 02:21:02 (4229) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-14 02:21:02 (4230) [[32mINFO[0m] 
* 2023-12-14 02:21:36 (4243) [[32mINFO[0m] 
* 2023-12-14 02:21:36 (4243) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-14 02:21:36 (4260) [[32mINFO[0m] 
* 2023-12-14 02:21:36 (1760) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-14 02:21:36 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-14 02:22:18 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-14 02:22:18 (2271) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lAbCrxUyLl/ea_profile.json
* 2023-12-14 02:22:20 (2294) [[32mINFO[0m] Backed up EA4 profile to /tmp/lAbCrxUyLl/ea_profile.json
* 2023-12-14 02:22:22 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.90.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.102.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-12-14 02:22:23 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-15 02:14:08 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-15 02:14:08 (1753) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-15 02:14:08 (4229) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-15 02:14:08 (4230) [[32mINFO[0m] 
* 2023-12-15 02:14:08 (4243) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-15 02:14:08 (4243) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-15 02:14:08 (4243) [[32mINFO[0m]               : epel extras updates
* 2023-12-15 02:14:08 (4243) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-15 02:14:08 (4260) [[32mINFO[0m] 
* 2023-12-15 02:14:08 (4229) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-15 02:14:08 (4230) [[32mINFO[0m] 
* 2023-12-15 02:14:41 (4243) [[32mINFO[0m] 
* 2023-12-15 02:14:41 (4243) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-15 02:14:42 (4260) [[32mINFO[0m] 
* 2023-12-15 02:14:42 (1760) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-15 02:14:42 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-15 02:15:11 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-15 02:15:11 (2271) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yDtATUeni9/ea_profile.json
* 2023-12-15 02:15:13 (2294) [[32mINFO[0m] Backed up EA4 profile to /tmp/yDtATUeni9/ea_profile.json
* 2023-12-15 02:15:15 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.90.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.102.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-12-15 02:15:16 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-15 15:48:43 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-15 15:48:43 (1753) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-15 15:48:43 (4229) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-15 15:48:43 (4230) [[32mINFO[0m] 
* 2023-12-15 15:48:43 (4243) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-15 15:48:43 (4243) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-15 15:48:43 (4243) [[32mINFO[0m]               : epel extras updates
* 2023-12-15 15:48:43 (4243) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-15 15:48:43 (4260) [[32mINFO[0m] 
* 2023-12-15 15:48:43 (4229) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-15 15:48:43 (4230) [[32mINFO[0m] 
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m] 
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m] 
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m] 
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m] 
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m] 
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m] 
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m] 
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]         or
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m] 
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]         compromise:
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m] 
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m] 
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-15 15:48:47 (4260) [[32mINFO[0m] 
* 2023-12-15 15:48:47 (1760) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-15 15:48:47 (1774) [[32mINFO[0m] Checking /scripts/sysup
* 2023-12-15 15:48:47 (4229) [[32mINFO[0m] Running: /scripts/sysup
* 2023-12-15 15:48:47 (4230) [[32mINFO[0m] 
* 2023-12-15 15:48:47 (4243) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-15 15:48:49 (4243) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-12-15 15:48:49 (4260) [[32mINFO[0m] 
* 2023-12-15 15:48:52 (1619) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-12-15 15:48:52 (1620) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-15 15:48:52 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-15 15:48:52 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-15 15:48:52 (2271) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4fLKWVZ2AY/ea_profile.json
* 2023-12-15 15:48:58 (299) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4fLKWVZ2AY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2273.
* 2023-12-15 15:48:58 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-16 02:14:00 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-16 02:14:00 (1753) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-16 02:14:00 (4229) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-16 02:14:00 (4230) [[32mINFO[0m] 
* 2023-12-16 02:14:01 (4243) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-16 02:14:01 (4243) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-16 02:14:01 (4243) [[32mINFO[0m]               : epel extras updates
* 2023-12-16 02:14:01 (4243) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-16 02:14:01 (4260) [[32mINFO[0m] 
* 2023-12-16 02:14:01 (4229) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-16 02:14:01 (4230) [[32mINFO[0m] 
* 2023-12-16 02:14:33 (4243) [[32mINFO[0m] 
* 2023-12-16 02:14:33 (4243) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-16 02:14:33 (4260) [[32mINFO[0m] 
* 2023-12-16 02:14:33 (1760) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-16 02:14:33 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-16 02:15:00 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-16 02:15:00 (2271) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hhe4rTOCiH/ea_profile.json
* 2023-12-16 02:15:02 (2294) [[32mINFO[0m] Backed up EA4 profile to /tmp/hhe4rTOCiH/ea_profile.json
* 2023-12-16 02:15:05 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.90.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.102.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-12-16 02:15:06 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-17 02:14:02 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-17 02:14:02 (1753) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-17 02:14:02 (4229) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-17 02:14:02 (4230) [[32mINFO[0m] 
* 2023-12-17 02:14:03 (4243) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-17 02:14:03 (4243) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-17 02:14:03 (4243) [[32mINFO[0m]               : epel extras updates
* 2023-12-17 02:14:03 (4243) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-17 02:14:03 (4260) [[32mINFO[0m] 
* 2023-12-17 02:14:03 (4229) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-17 02:14:03 (4230) [[32mINFO[0m] 
* 2023-12-17 02:14:34 (4243) [[32mINFO[0m] 
* 2023-12-17 02:14:34 (4243) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-17 02:14:34 (4260) [[32mINFO[0m] 
* 2023-12-17 02:14:34 (1760) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-17 02:14:34 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-17 02:14:57 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-17 02:14:58 (2271) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RjrWQyxVFu/ea_profile.json
* 2023-12-17 02:15:00 (2294) [[32mINFO[0m] Backed up EA4 profile to /tmp/RjrWQyxVFu/ea_profile.json
* 2023-12-17 02:15:03 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.90.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.102.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-12-17 02:15:04 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-18 02:13:27 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-18 02:13:27 (1753) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-18 02:13:27 (4229) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-18 02:13:27 (4230) [[32mINFO[0m] 
* 2023-12-18 02:13:27 (4243) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-18 02:13:27 (4243) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-18 02:13:27 (4243) [[32mINFO[0m]               : epel extras updates
* 2023-12-18 02:13:28 (4243) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-18 02:13:28 (4260) [[32mINFO[0m] 
* 2023-12-18 02:13:28 (4229) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-18 02:13:28 (4230) [[32mINFO[0m] 
* 2023-12-18 02:13:58 (4243) [[32mINFO[0m] 
* 2023-12-18 02:13:58 (4243) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-18 02:13:58 (4260) [[32mINFO[0m] 
* 2023-12-18 02:13:58 (1760) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-18 02:13:58 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-18 02:14:24 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-18 02:14:24 (2271) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/V4FdZiupcG/ea_profile.json
* 2023-12-18 02:14:26 (2294) [[32mINFO[0m] Backed up EA4 profile to /tmp/V4FdZiupcG/ea_profile.json
* 2023-12-18 02:14:28 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.90.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.102.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-12-18 02:14:29 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-19 02:13:35 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-19 02:13:35 (1753) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-19 02:13:35 (4229) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-19 02:13:35 (4230) [[32mINFO[0m] 
* 2023-12-19 02:13:36 (4243) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-19 02:13:36 (4243) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-19 02:13:36 (4243) [[32mINFO[0m]               : epel extras updates
* 2023-12-19 02:13:36 (4243) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-19 02:13:36 (4260) [[32mINFO[0m] 
* 2023-12-19 02:13:36 (4229) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-19 02:13:36 (4230) [[32mINFO[0m] 
* 2023-12-19 02:14:22 (4243) [[32mINFO[0m] 
* 2023-12-19 02:14:22 (4243) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-19 02:14:23 (4260) [[32mINFO[0m] 
* 2023-12-19 02:14:23 (1760) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-19 02:14:23 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-19 02:14:49 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-19 02:14:49 (2271) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/h959VF5yoo/ea_profile.json
* 2023-12-19 02:14:51 (2294) [[32mINFO[0m] Backed up EA4 profile to /tmp/h959VF5yoo/ea_profile.json
* 2023-12-19 02:14:54 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.90.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.102.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-12-19 02:14:55 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-20 02:13:25 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-20 02:13:25 (1753) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-20 02:13:25 (4229) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-20 02:13:25 (4230) [[32mINFO[0m] 
* 2023-12-20 02:13:25 (4243) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-20 02:13:25 (4243) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-20 02:13:25 (4243) [[32mINFO[0m]               : epel extras updates
* 2023-12-20 02:13:25 (4243) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-20 02:13:25 (4260) [[32mINFO[0m] 
* 2023-12-20 02:13:25 (4229) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-20 02:13:25 (4230) [[32mINFO[0m] 
* 2023-12-20 02:13:57 (4243) [[32mINFO[0m] 
* 2023-12-20 02:13:57 (4243) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-20 02:13:57 (4260) [[32mINFO[0m] 
* 2023-12-20 02:13:57 (1760) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-20 02:13:57 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-20 02:14:23 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-20 02:14:23 (2271) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/p29Lws4r83/ea_profile.json
* 2023-12-20 02:14:24 (2294) [[32mINFO[0m] Backed up EA4 profile to /tmp/p29Lws4r83/ea_profile.json
* 2023-12-20 02:14:27 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.90.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.102.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2023-12-20 02:14:28 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-21 02:15:20 (569) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-21 02:15:20 (1753) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-21 02:15:20 (4229) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-21 02:15:20 (4230) [[32mINFO[0m] 
* 2023-12-21 02:15:20 (4243) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-21 02:15:21 (4243) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-21 02:15:21 (4243) [[32mINFO[0m]               : epel extras updates
* 2023-12-21 02:15:21 (4243) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-21 02:15:21 (4260) [[32mINFO[0m] 
* 2023-12-21 02:15:21 (4229) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-21 02:15:21 (4230) [[32mINFO[0m] 
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m] 
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m] 
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m] 
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m] 
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m] 
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m] 
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m] 
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]         or
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m] 
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]         compromise:
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m] 
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m] 
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-21 02:15:24 (4260) [[32mINFO[0m] 
* 2023-12-21 02:15:24 (1760) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-21 02:15:24 (1774) [[32mINFO[0m] Checking /scripts/sysup
* 2023-12-21 02:15:24 (4229) [[32mINFO[0m] Running: /scripts/sysup
* 2023-12-21 02:15:24 (4230) [[32mINFO[0m] 
* 2023-12-21 02:15:24 (4243) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-21 02:15:25 (4243) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-12-21 02:15:25 (4260) [[32mINFO[0m] 
* 2023-12-21 02:15:29 (1619) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-12-21 02:15:29 (1620) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-21 02:15:29 (155) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-21 02:15:29 (815) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-21 02:15:30 (2271) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/555yVdpPok/ea_profile.json
* 2023-12-21 02:15:35 (299) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/555yVdpPok/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2273.
* 2023-12-21 02:15:35 (260) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-22 02:12:41 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-22 02:12:41 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-22 02:12:41 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-22 02:12:41 (4251) [[32mINFO[0m] 
* 2023-12-22 02:12:42 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-22 02:12:42 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-22 02:12:42 (4264) [[32mINFO[0m]               : epel extras updates
* 2023-12-22 02:12:42 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-22 02:12:42 (4281) [[32mINFO[0m] 
* 2023-12-22 02:12:42 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-22 02:12:42 (4251) [[32mINFO[0m] 
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]         or
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]         compromise:
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-22 02:12:46 (4281) [[32mINFO[0m] 
* 2023-12-22 02:12:46 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-22 02:12:46 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2023-12-22 02:12:46 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2023-12-22 02:12:46 (4251) [[32mINFO[0m] 
* 2023-12-22 02:12:46 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-22 02:12:47 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-12-22 02:12:47 (4281) [[32mINFO[0m] 
* 2023-12-22 02:12:51 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-12-22 02:12:51 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-22 02:12:51 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-22 02:12:51 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-22 02:12:52 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9ixPZKwlAW/ea_profile.json
* 2023-12-22 02:12:57 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9ixPZKwlAW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-22 02:12:57 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-22 15:47:40 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-22 15:47:40 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-22 15:47:40 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-22 15:47:40 (4251) [[32mINFO[0m] 
* 2023-12-22 15:47:41 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-22 15:47:41 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-22 15:47:41 (4264) [[32mINFO[0m]               : epel extras updates
* 2023-12-22 15:47:41 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-22 15:47:41 (4281) [[32mINFO[0m] 
* 2023-12-22 15:47:41 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-22 15:47:41 (4251) [[32mINFO[0m] 
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m] 
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m] 
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m] 
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m] 
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m] 
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m] 
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m] 
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]         or
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m] 
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]         compromise:
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m] 
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m] 
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-22 15:47:45 (4281) [[32mINFO[0m] 
* 2023-12-22 15:47:45 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-22 15:47:45 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2023-12-22 15:47:45 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2023-12-22 15:47:45 (4251) [[32mINFO[0m] 
* 2023-12-22 15:47:45 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-22 15:47:46 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-12-22 15:47:46 (4281) [[32mINFO[0m] 
* 2023-12-22 15:47:48 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-12-22 15:47:48 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-22 15:47:48 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-22 15:47:49 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-22 15:47:49 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/i34HE0_9cs/ea_profile.json
* 2023-12-22 15:47:54 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/i34HE0_9cs/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-22 15:47:54 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-23 02:13:18 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-23 02:13:18 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-23 02:13:18 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-23 02:13:18 (4251) [[32mINFO[0m] 
* 2023-12-23 02:13:19 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-23 02:13:19 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-23 02:13:19 (4264) [[32mINFO[0m]               : epel extras updates
* 2023-12-23 02:13:19 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-23 02:13:19 (4281) [[32mINFO[0m] 
* 2023-12-23 02:13:19 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-23 02:13:19 (4251) [[32mINFO[0m] 
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m] 
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m] 
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m] 
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m] 
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m] 
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m] 
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m] 
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]         or
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m] 
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]         compromise:
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m] 
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m] 
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-23 02:13:23 (4281) [[32mINFO[0m] 
* 2023-12-23 02:13:23 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-23 02:13:23 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2023-12-23 02:13:23 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2023-12-23 02:13:23 (4251) [[32mINFO[0m] 
* 2023-12-23 02:13:23 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-23 02:13:24 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-12-23 02:13:24 (4281) [[32mINFO[0m] 
* 2023-12-23 02:13:28 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-12-23 02:13:28 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-23 02:13:28 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-23 02:13:28 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-23 02:13:29 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dPVCrsLp3V/ea_profile.json
* 2023-12-23 02:13:34 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dPVCrsLp3V/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-23 02:13:34 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-24 02:13:28 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-24 02:13:28 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-24 02:13:28 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-24 02:13:28 (4251) [[32mINFO[0m] 
* 2023-12-24 02:13:28 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-24 02:13:29 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-24 02:13:29 (4264) [[32mINFO[0m]               : epel extras updates
* 2023-12-24 02:13:29 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-24 02:13:29 (4281) [[32mINFO[0m] 
* 2023-12-24 02:13:29 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-24 02:13:29 (4251) [[32mINFO[0m] 
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m] 
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m] 
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m] 
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m] 
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m] 
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m] 
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m] 
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]         or
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m] 
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]         compromise:
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m] 
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m] 
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-24 02:13:36 (4281) [[32mINFO[0m] 
* 2023-12-24 02:13:36 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-24 02:13:36 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2023-12-24 02:13:36 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2023-12-24 02:13:36 (4251) [[32mINFO[0m] 
* 2023-12-24 02:13:36 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-24 02:13:37 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-12-24 02:13:37 (4281) [[32mINFO[0m] 
* 2023-12-24 02:13:42 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-12-24 02:13:42 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-24 02:13:42 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-24 02:13:43 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-24 02:13:43 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NgxTWIIx3P/ea_profile.json
* 2023-12-24 02:13:51 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NgxTWIIx3P/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-24 02:13:51 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-25 02:16:11 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2023-12-25 02:16:12 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-25 02:16:12 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-25 02:16:12 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-25 02:16:12 (4251) [[32mINFO[0m] 
* 2023-12-25 02:16:12 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-25 02:16:13 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-25 02:16:13 (4264) [[32mINFO[0m]               : epel extras updates
* 2023-12-25 02:16:13 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-25 02:16:13 (4281) [[32mINFO[0m] 
* 2023-12-25 02:16:13 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-25 02:16:13 (4251) [[32mINFO[0m] 
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m] 
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m] 
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m] 
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m] 
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m] 
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m] 
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m] 
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]         or
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m] 
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]         compromise:
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m] 
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m] 
* 2023-12-25 02:16:16 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-25 02:16:17 (4281) [[32mINFO[0m] 
* 2023-12-25 02:16:17 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-25 02:16:17 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2023-12-25 02:16:17 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2023-12-25 02:16:17 (4251) [[32mINFO[0m] 
* 2023-12-25 02:16:17 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-25 02:16:18 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-12-25 02:16:18 (4281) [[32mINFO[0m] 
* 2023-12-25 02:16:21 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-12-25 02:16:21 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-25 02:16:21 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-25 02:16:21 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-25 02:16:22 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UwDgzEsea9/ea_profile.json
* 2023-12-25 02:16:57 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UwDgzEsea9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-25 02:16:57 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-26 02:12:40 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-26 02:12:40 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-26 02:12:40 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-26 02:12:40 (4251) [[32mINFO[0m] 
* 2023-12-26 02:12:40 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-26 02:12:41 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-26 02:12:41 (4264) [[32mINFO[0m]               : epel extras updates
* 2023-12-26 02:12:41 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-26 02:12:41 (4281) [[32mINFO[0m] 
* 2023-12-26 02:12:41 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-26 02:12:41 (4251) [[32mINFO[0m] 
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m] 
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m] 
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m] 
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m] 
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m] 
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m] 
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m] 
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]         or
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m] 
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]         compromise:
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m] 
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m] 
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-26 02:12:45 (4281) [[32mINFO[0m] 
* 2023-12-26 02:12:45 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-26 02:12:45 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2023-12-26 02:12:45 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2023-12-26 02:12:45 (4251) [[32mINFO[0m] 
* 2023-12-26 02:12:45 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-26 02:12:46 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-12-26 02:12:46 (4281) [[32mINFO[0m] 
* 2023-12-26 02:12:51 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-12-26 02:12:51 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-26 02:12:51 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-26 02:12:51 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-26 02:12:51 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pJKbILt4Ea/ea_profile.json
* 2023-12-26 02:12:57 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pJKbILt4Ea/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-26 02:12:57 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-27 02:12:42 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-27 02:12:42 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-27 02:12:42 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-27 02:12:42 (4251) [[32mINFO[0m] 
* 2023-12-27 02:12:42 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-27 02:12:42 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-27 02:12:42 (4264) [[32mINFO[0m]               : epel extras updates
* 2023-12-27 02:12:42 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-27 02:12:42 (4281) [[32mINFO[0m] 
* 2023-12-27 02:12:42 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-27 02:12:42 (4251) [[32mINFO[0m] 
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]         or
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]         compromise:
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m] 
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-27 02:12:46 (4281) [[32mINFO[0m] 
* 2023-12-27 02:12:46 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-27 02:12:46 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2023-12-27 02:12:46 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2023-12-27 02:12:46 (4251) [[32mINFO[0m] 
* 2023-12-27 02:12:46 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-27 02:12:47 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-12-27 02:12:47 (4281) [[32mINFO[0m] 
* 2023-12-27 02:12:50 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-12-27 02:12:50 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-27 02:12:50 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-27 02:12:50 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-27 02:12:50 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zFhWMyQPb0/ea_profile.json
* 2023-12-27 02:12:55 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zFhWMyQPb0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-27 02:12:55 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-28 02:12:40 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-28 02:12:40 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-28 02:12:40 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-28 02:12:40 (4251) [[32mINFO[0m] 
* 2023-12-28 02:12:40 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-28 02:12:40 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-28 02:12:40 (4264) [[32mINFO[0m]               : epel extras updates
* 2023-12-28 02:12:40 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-28 02:12:40 (4281) [[32mINFO[0m] 
* 2023-12-28 02:12:40 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-28 02:12:40 (4251) [[32mINFO[0m] 
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m] 
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m] 
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m] 
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m] 
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m] 
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m] 
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m] 
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]         or
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m] 
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]         compromise:
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m] 
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m] 
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-28 02:13:14 (4281) [[32mINFO[0m] 
* 2023-12-28 02:13:14 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-28 02:13:14 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2023-12-28 02:13:14 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2023-12-28 02:13:14 (4251) [[32mINFO[0m] 
* 2023-12-28 02:13:14 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-28 02:13:16 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-12-28 02:13:16 (4281) [[32mINFO[0m] 
* 2023-12-28 02:13:19 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-12-28 02:13:19 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-28 02:13:19 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-28 02:13:20 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-28 02:13:20 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OTiuEGq6kG/ea_profile.json
* 2023-12-28 02:13:26 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OTiuEGq6kG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-28 02:13:26 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-29 02:12:46 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-29 02:12:46 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-29 02:12:46 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-29 02:12:46 (4251) [[32mINFO[0m] 
* 2023-12-29 02:12:46 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-29 02:12:46 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-29 02:12:46 (4264) [[32mINFO[0m]               : epel extras updates
* 2023-12-29 02:12:46 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-29 02:12:46 (4281) [[32mINFO[0m] 
* 2023-12-29 02:12:46 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-29 02:12:46 (4251) [[32mINFO[0m] 
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m] 
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m] 
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m] 
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m] 
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m] 
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m] 
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m] 
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]         or
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m] 
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]         compromise:
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m] 
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m] 
* 2023-12-29 02:12:51 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-29 02:12:51 (4281) [[32mINFO[0m] 
* 2023-12-29 02:12:51 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-29 02:12:51 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2023-12-29 02:12:51 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2023-12-29 02:12:51 (4251) [[32mINFO[0m] 
* 2023-12-29 02:12:52 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-29 02:12:53 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-12-29 02:12:53 (4281) [[32mINFO[0m] 
* 2023-12-29 02:12:56 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-12-29 02:12:56 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-29 02:12:56 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-29 02:12:57 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-29 02:12:59 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rcSWo544yn/ea_profile.json
* 2023-12-29 02:13:07 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rcSWo544yn/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-29 02:13:07 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-29 15:47:17 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-29 15:47:17 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-29 15:47:17 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-29 15:47:17 (4251) [[32mINFO[0m] 
* 2023-12-29 15:47:17 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-29 15:47:17 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-29 15:47:17 (4264) [[32mINFO[0m]               : epel extras updates
* 2023-12-29 15:47:17 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-29 15:47:17 (4281) [[32mINFO[0m] 
* 2023-12-29 15:47:17 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-29 15:47:17 (4251) [[32mINFO[0m] 
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m] 
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m] 
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m] 
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m] 
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m] 
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m] 
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m] 
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]         or
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m] 
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]         compromise:
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m] 
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m] 
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-29 15:47:27 (4281) [[32mINFO[0m] 
* 2023-12-29 15:47:27 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-29 15:47:27 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2023-12-29 15:47:27 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2023-12-29 15:47:27 (4251) [[32mINFO[0m] 
* 2023-12-29 15:47:27 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-29 15:47:28 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-12-29 15:47:28 (4281) [[32mINFO[0m] 
* 2023-12-29 15:47:35 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-12-29 15:47:35 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-29 15:47:35 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-29 15:47:35 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-29 15:47:35 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/o6voEoPtkD/ea_profile.json
* 2023-12-29 15:47:45 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/o6voEoPtkD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-29 15:47:45 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-30 02:13:23 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-30 02:13:23 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-30 02:13:23 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-30 02:13:23 (4251) [[32mINFO[0m] 
* 2023-12-30 02:13:23 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-30 02:13:23 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-30 02:13:23 (4264) [[32mINFO[0m]               : epel extras updates
* 2023-12-30 02:13:23 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-30 02:13:23 (4281) [[32mINFO[0m] 
* 2023-12-30 02:13:23 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-30 02:13:23 (4251) [[32mINFO[0m] 
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m] 
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m] 
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m] 
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m] 
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m] 
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m] 
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m] 
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]         or
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m] 
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]         compromise:
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m] 
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m] 
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-30 02:13:29 (4281) [[32mINFO[0m] 
* 2023-12-30 02:13:29 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-30 02:13:29 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2023-12-30 02:13:29 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2023-12-30 02:13:29 (4251) [[32mINFO[0m] 
* 2023-12-30 02:13:29 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-30 02:13:31 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-12-30 02:13:31 (4281) [[32mINFO[0m] 
* 2023-12-30 02:13:34 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-12-30 02:13:34 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-30 02:13:34 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-30 02:13:34 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-30 02:13:34 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sgMg0v6PgO/ea_profile.json
* 2023-12-30 02:13:40 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sgMg0v6PgO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-30 02:13:40 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-31 02:13:25 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2023-12-31 02:13:25 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2023-12-31 02:13:25 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2023-12-31 02:13:25 (4251) [[32mINFO[0m] 
* 2023-12-31 02:13:25 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-31 02:13:25 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2023-12-31 02:13:25 (4264) [[32mINFO[0m]               : epel extras updates
* 2023-12-31 02:13:25 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2023-12-31 02:13:25 (4281) [[32mINFO[0m] 
* 2023-12-31 02:13:25 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2023-12-31 02:13:25 (4251) [[32mINFO[0m] 
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m] 
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m] 
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m] 
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m] 
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m] 
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m] 
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m] 
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]         or
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m] 
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]         compromise:
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m] 
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m] 
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-31 02:13:30 (4281) [[32mINFO[0m] 
* 2023-12-31 02:13:30 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-31 02:13:30 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2023-12-31 02:13:30 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2023-12-31 02:13:30 (4251) [[32mINFO[0m] 
* 2023-12-31 02:13:30 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-31 02:13:31 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2023-12-31 02:13:31 (4281) [[32mINFO[0m] 
* 2023-12-31 02:13:34 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2023-12-31 02:13:34 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2023-12-31 02:13:34 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-31 02:13:35 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-31 02:13:35 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EuZ7celxER/ea_profile.json
* 2023-12-31 02:13:41 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EuZ7celxER/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2023-12-31 02:13:41 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-01 02:12:49 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-01 02:12:49 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-01 02:12:49 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-01 02:12:49 (4251) [[32mINFO[0m] 
* 2024-01-01 02:12:49 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-01 02:12:49 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-01 02:12:49 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-01 02:12:49 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-01 02:12:49 (4281) [[32mINFO[0m] 
* 2024-01-01 02:12:49 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-01 02:12:49 (4251) [[32mINFO[0m] 
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m] 
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m] 
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m] 
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m] 
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m] 
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m] 
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m] 
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]         or
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m] 
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]         compromise:
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m] 
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m] 
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-01 02:12:54 (4281) [[32mINFO[0m] 
* 2024-01-01 02:12:54 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-01 02:12:54 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-01 02:12:54 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-01 02:12:54 (4251) [[32mINFO[0m] 
* 2024-01-01 02:12:54 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-01 02:12:55 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-01 02:12:55 (4281) [[32mINFO[0m] 
* 2024-01-01 02:12:59 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-01 02:12:59 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-01 02:12:59 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-01 02:12:59 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-01 02:12:59 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tBJRm01lp2/ea_profile.json
* 2024-01-01 02:13:06 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tBJRm01lp2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-01 02:13:06 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-02 02:12:46 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-02 02:12:46 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-02 02:12:46 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-02 02:12:46 (4251) [[32mINFO[0m] 
* 2024-01-02 02:12:46 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-02 02:12:46 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-02 02:12:46 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-02 02:12:46 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-02 02:12:46 (4281) [[32mINFO[0m] 
* 2024-01-02 02:12:46 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-02 02:12:46 (4251) [[32mINFO[0m] 
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m] 
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m] 
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m] 
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m] 
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m] 
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m] 
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m] 
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]         or
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m] 
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]         compromise:
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m] 
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m] 
* 2024-01-02 02:12:50 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-02 02:12:50 (4281) [[32mINFO[0m] 
* 2024-01-02 02:12:50 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-02 02:12:50 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-02 02:12:50 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-02 02:12:50 (4251) [[32mINFO[0m] 
* 2024-01-02 02:12:51 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-02 02:12:52 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-02 02:12:52 (4281) [[32mINFO[0m] 
* 2024-01-02 02:12:56 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-02 02:12:56 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-02 02:12:56 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-02 02:12:56 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-02 02:12:56 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZjgxbK1Jow/ea_profile.json
* 2024-01-02 02:13:02 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZjgxbK1Jow/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-02 02:13:02 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-03 02:12:45 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-03 02:12:45 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-03 02:12:45 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-03 02:12:45 (4251) [[32mINFO[0m] 
* 2024-01-03 02:12:45 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-03 02:12:45 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-03 02:12:45 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-03 02:12:45 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-03 02:12:45 (4281) [[32mINFO[0m] 
* 2024-01-03 02:12:45 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-03 02:12:45 (4251) [[32mINFO[0m] 
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m] 
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m] 
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m] 
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m] 
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m] 
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m] 
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m] 
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]         or
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m] 
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]         compromise:
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m] 
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m] 
* 2024-01-03 02:13:19 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-03 02:13:19 (4281) [[32mINFO[0m] 
* 2024-01-03 02:13:19 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-03 02:13:19 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-03 02:13:19 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-03 02:13:19 (4251) [[32mINFO[0m] 
* 2024-01-03 02:13:20 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-03 02:13:23 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-03 02:13:23 (4281) [[32mINFO[0m] 
* 2024-01-03 02:13:27 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-03 02:13:27 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-03 02:13:27 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-03 02:13:27 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-03 02:13:27 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Vy982krEmP/ea_profile.json
* 2024-01-03 02:13:34 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Vy982krEmP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-03 02:13:34 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-04 02:12:34 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-04 02:12:34 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-04 02:12:34 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-04 02:12:34 (4251) [[32mINFO[0m] 
* 2024-01-04 02:12:34 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-04 02:12:34 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-04 02:12:34 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-04 02:12:34 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-04 02:12:34 (4281) [[32mINFO[0m] 
* 2024-01-04 02:12:34 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-04 02:12:34 (4251) [[32mINFO[0m] 
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]         or
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]         compromise:
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-04 02:12:39 (4281) [[32mINFO[0m] 
* 2024-01-04 02:12:39 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-04 02:12:39 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-04 02:12:39 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-04 02:12:39 (4251) [[32mINFO[0m] 
* 2024-01-04 02:12:39 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-04 02:12:41 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-04 02:12:41 (4281) [[32mINFO[0m] 
* 2024-01-04 02:12:44 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-04 02:12:44 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-04 02:12:44 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-04 02:12:45 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-04 02:12:45 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Fw7VykYFNR/ea_profile.json
* 2024-01-04 02:12:51 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Fw7VykYFNR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-04 02:12:51 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-05 02:12:47 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-05 02:12:47 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-05 02:12:47 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-05 02:12:47 (4251) [[32mINFO[0m] 
* 2024-01-05 02:12:47 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-05 02:12:48 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-05 02:12:48 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-05 02:12:48 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-05 02:12:48 (4281) [[32mINFO[0m] 
* 2024-01-05 02:12:48 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-05 02:12:48 (4251) [[32mINFO[0m] 
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m] 
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m] 
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m] 
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m] 
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m] 
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m] 
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m] 
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]         or
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m] 
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]         compromise:
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m] 
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m] 
* 2024-01-05 02:12:55 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-05 02:12:55 (4281) [[32mINFO[0m] 
* 2024-01-05 02:12:55 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-05 02:12:55 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-05 02:12:55 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-05 02:12:55 (4251) [[32mINFO[0m] 
* 2024-01-05 02:12:56 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-05 02:12:57 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-05 02:12:57 (4281) [[32mINFO[0m] 
* 2024-01-05 02:13:01 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-05 02:13:01 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-05 02:13:01 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-05 02:13:01 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-05 02:13:01 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WFyIyXTe_p/ea_profile.json
* 2024-01-05 02:13:11 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WFyIyXTe_p/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-05 02:13:11 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-05 15:47:12 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-05 15:47:12 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-05 15:47:12 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-05 15:47:12 (4251) [[32mINFO[0m] 
* 2024-01-05 15:47:12 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-05 15:47:13 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-05 15:47:13 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-05 15:47:13 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-05 15:47:13 (4281) [[32mINFO[0m] 
* 2024-01-05 15:47:13 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-05 15:47:13 (4251) [[32mINFO[0m] 
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m] 
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m] 
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m] 
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m] 
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m] 
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m] 
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m] 
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]         or
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m] 
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]         compromise:
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m] 
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m] 
* 2024-01-05 15:47:18 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-05 15:47:18 (4281) [[32mINFO[0m] 
* 2024-01-05 15:47:18 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-05 15:47:18 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-05 15:47:18 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-05 15:47:18 (4251) [[32mINFO[0m] 
* 2024-01-05 15:47:19 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-05 15:47:20 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-05 15:47:20 (4281) [[32mINFO[0m] 
* 2024-01-05 15:47:23 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-05 15:47:23 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-05 15:47:23 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-05 15:47:24 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-05 15:47:24 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DHQPWsvwUV/ea_profile.json
* 2024-01-05 15:47:34 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DHQPWsvwUV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-05 15:47:34 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-06 02:13:48 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-06 02:13:48 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-06 02:13:48 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-06 02:13:48 (4251) [[32mINFO[0m] 
* 2024-01-06 02:13:48 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-06 02:13:48 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-06 02:13:48 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-06 02:13:48 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-06 02:13:48 (4281) [[32mINFO[0m] 
* 2024-01-06 02:13:48 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-06 02:13:48 (4251) [[32mINFO[0m] 
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m] 
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m] 
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m] 
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m] 
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m] 
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m] 
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m] 
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]         or
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m] 
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]         compromise:
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m] 
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m] 
* 2024-01-06 02:13:52 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-06 02:13:52 (4281) [[32mINFO[0m] 
* 2024-01-06 02:13:52 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-06 02:13:52 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-06 02:13:52 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-06 02:13:52 (4251) [[32mINFO[0m] 
* 2024-01-06 02:13:53 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-06 02:13:54 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-06 02:13:54 (4281) [[32mINFO[0m] 
* 2024-01-06 02:13:57 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-06 02:13:57 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-06 02:13:57 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-06 02:13:58 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-06 02:13:58 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iP9dz5qB_C/ea_profile.json
* 2024-01-06 02:14:04 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iP9dz5qB_C/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-06 02:14:04 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-07 02:13:18 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-07 02:13:18 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-07 02:13:18 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-07 02:13:18 (4251) [[32mINFO[0m] 
* 2024-01-07 02:13:18 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-07 02:13:18 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-07 02:13:18 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-07 02:13:18 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-07 02:13:18 (4281) [[32mINFO[0m] 
* 2024-01-07 02:13:18 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-07 02:13:18 (4251) [[32mINFO[0m] 
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m] 
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m] 
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m] 
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m] 
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m] 
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m] 
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m] 
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]         or
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m] 
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]         compromise:
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m] 
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m] 
* 2024-01-07 02:13:22 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-07 02:13:22 (4281) [[32mINFO[0m] 
* 2024-01-07 02:13:22 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-07 02:13:22 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-07 02:13:22 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-07 02:13:22 (4251) [[32mINFO[0m] 
* 2024-01-07 02:13:23 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-07 02:13:24 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-07 02:13:24 (4281) [[32mINFO[0m] 
* 2024-01-07 02:13:28 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-07 02:13:28 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-07 02:13:28 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-07 02:13:29 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-07 02:13:30 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RshjFoWVoh/ea_profile.json
* 2024-01-07 02:13:37 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RshjFoWVoh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-07 02:13:37 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-08 02:12:33 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-08 02:12:33 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-08 02:12:33 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-08 02:12:33 (4251) [[32mINFO[0m] 
* 2024-01-08 02:12:33 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-08 02:12:34 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-08 02:12:34 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-08 02:12:34 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-08 02:12:34 (4281) [[32mINFO[0m] 
* 2024-01-08 02:12:34 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-08 02:12:34 (4251) [[32mINFO[0m] 
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m] 
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m] 
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m] 
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m] 
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m] 
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m] 
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m] 
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]         or
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m] 
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]         compromise:
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m] 
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m] 
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-08 02:12:38 (4281) [[32mINFO[0m] 
* 2024-01-08 02:12:38 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-08 02:12:38 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-08 02:12:38 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-08 02:12:38 (4251) [[32mINFO[0m] 
* 2024-01-08 02:12:38 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-08 02:12:40 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-08 02:12:40 (4281) [[32mINFO[0m] 
* 2024-01-08 02:12:43 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-08 02:12:43 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-08 02:12:43 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-08 02:12:44 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-08 02:12:45 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/eOHgEzJA_l/ea_profile.json
* 2024-01-08 02:12:51 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/eOHgEzJA_l/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-08 02:12:51 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-09 02:12:32 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-09 02:12:32 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-09 02:12:32 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-09 02:12:32 (4251) [[32mINFO[0m] 
* 2024-01-09 02:12:32 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-09 02:12:32 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-09 02:12:32 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-09 02:12:32 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-09 02:12:32 (4281) [[32mINFO[0m] 
* 2024-01-09 02:12:32 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-09 02:12:32 (4251) [[32mINFO[0m] 
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]         or
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]         compromise:
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-09 02:12:37 (4281) [[32mINFO[0m] 
* 2024-01-09 02:12:37 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-09 02:12:37 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-09 02:12:37 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-09 02:12:37 (4251) [[32mINFO[0m] 
* 2024-01-09 02:12:37 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-09 02:12:38 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-09 02:12:38 (4281) [[32mINFO[0m] 
* 2024-01-09 02:12:42 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-09 02:12:42 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-09 02:12:42 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-09 02:12:42 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-09 02:12:42 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mstDwkANGY/ea_profile.json
* 2024-01-09 02:12:48 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mstDwkANGY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-09 02:12:48 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-10 02:12:28 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-10 02:12:28 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-10 02:12:28 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-10 02:12:28 (4251) [[32mINFO[0m] 
* 2024-01-10 02:12:28 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-10 02:12:28 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-10 02:12:28 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-10 02:12:28 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-10 02:12:29 (4281) [[32mINFO[0m] 
* 2024-01-10 02:12:29 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-10 02:12:29 (4251) [[32mINFO[0m] 
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m] 
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m] 
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m] 
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m] 
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m] 
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m] 
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m] 
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]         or
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m] 
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]         compromise:
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m] 
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m] 
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-10 02:12:33 (4281) [[32mINFO[0m] 
* 2024-01-10 02:12:33 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-10 02:12:33 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-10 02:12:33 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-10 02:12:33 (4251) [[32mINFO[0m] 
* 2024-01-10 02:12:33 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-10 02:12:34 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-10 02:12:34 (4281) [[32mINFO[0m] 
* 2024-01-10 02:12:38 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-10 02:12:38 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-10 02:12:38 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-10 02:12:38 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-10 02:12:38 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1VQL1rfwrQ/ea_profile.json
* 2024-01-10 02:12:44 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1VQL1rfwrQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-10 02:12:44 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-11 02:12:36 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-11 02:12:36 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-11 02:12:36 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-11 02:12:36 (4251) [[32mINFO[0m] 
* 2024-01-11 02:12:36 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-11 02:12:36 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-11 02:12:36 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-11 02:12:36 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-11 02:12:36 (4281) [[32mINFO[0m] 
* 2024-01-11 02:12:36 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-11 02:12:36 (4251) [[32mINFO[0m] 
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]         or
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]         compromise:
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-11 02:12:40 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-11 02:12:40 (4281) [[32mINFO[0m] 
* 2024-01-11 02:12:40 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-11 02:12:40 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-11 02:12:40 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-11 02:12:40 (4251) [[32mINFO[0m] 
* 2024-01-11 02:12:41 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-11 02:12:42 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-11 02:12:42 (4281) [[32mINFO[0m] 
* 2024-01-11 02:12:46 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-11 02:12:46 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-11 02:12:46 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-11 02:12:46 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-11 02:12:46 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rTmq0bEvZV/ea_profile.json
* 2024-01-11 02:12:53 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rTmq0bEvZV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-11 02:12:53 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-12 02:12:33 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-12 02:12:33 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-12 02:12:33 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-12 02:12:33 (4251) [[32mINFO[0m] 
* 2024-01-12 02:12:33 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-12 02:12:34 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-12 02:12:34 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-12 02:12:34 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-12 02:12:34 (4281) [[32mINFO[0m] 
* 2024-01-12 02:12:34 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-12 02:12:34 (4251) [[32mINFO[0m] 
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m] 
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m] 
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m] 
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m] 
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m] 
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m] 
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m] 
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]         or
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m] 
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]         compromise:
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m] 
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m] 
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-12 02:12:41 (4281) [[32mINFO[0m] 
* 2024-01-12 02:12:41 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-12 02:12:41 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-12 02:12:41 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-12 02:12:41 (4251) [[32mINFO[0m] 
* 2024-01-12 02:12:41 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-12 02:12:42 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-12 02:12:42 (4281) [[32mINFO[0m] 
* 2024-01-12 02:12:46 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-12 02:12:46 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-12 02:12:46 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-12 02:12:46 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-12 02:12:47 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dhc6fxRoME/ea_profile.json
* 2024-01-12 02:12:55 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dhc6fxRoME/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-12 02:12:55 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-12 15:47:41 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-12 15:47:41 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-12 15:47:41 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-12 15:47:41 (4251) [[32mINFO[0m] 
* 2024-01-12 15:47:42 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-12 15:47:42 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-12 15:47:42 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-12 15:47:42 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-12 15:47:42 (4281) [[32mINFO[0m] 
* 2024-01-12 15:47:42 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-12 15:47:42 (4251) [[32mINFO[0m] 
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m] 
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m] 
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m] 
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m] 
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m] 
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m] 
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m] 
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]         or
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m] 
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]         compromise:
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m] 
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m] 
* 2024-01-12 15:48:19 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-12 15:48:19 (4281) [[32mINFO[0m] 
* 2024-01-12 15:48:19 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-12 15:48:19 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-12 15:48:19 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-12 15:48:19 (4251) [[32mINFO[0m] 
* 2024-01-12 15:48:20 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-12 15:48:21 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-12 15:48:21 (4281) [[32mINFO[0m] 
* 2024-01-12 15:48:25 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-12 15:48:25 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-12 15:48:25 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-12 15:48:25 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-12 15:48:25 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0yFYO1iuIR/ea_profile.json
* 2024-01-12 15:49:08 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0yFYO1iuIR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-12 15:49:08 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-13 02:14:19 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-13 02:14:19 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-13 02:14:19 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-13 02:14:19 (4251) [[32mINFO[0m] 
* 2024-01-13 02:14:19 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-13 02:14:19 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-13 02:14:19 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-13 02:14:19 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-13 02:14:19 (4281) [[32mINFO[0m] 
* 2024-01-13 02:14:19 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-13 02:14:19 (4251) [[32mINFO[0m] 
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m] 
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m] 
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m] 
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m] 
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m] 
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m] 
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m] 
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]         or
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m] 
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]         compromise:
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m] 
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m] 
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-13 02:14:23 (4281) [[32mINFO[0m] 
* 2024-01-13 02:14:23 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-13 02:14:23 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-13 02:14:23 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-13 02:14:23 (4251) [[32mINFO[0m] 
* 2024-01-13 02:14:23 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-13 02:14:26 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-13 02:14:26 (4281) [[32mINFO[0m] 
* 2024-01-13 02:14:30 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-13 02:14:30 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-13 02:14:30 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-13 02:14:30 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-13 02:14:31 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pZfttxBuL8/ea_profile.json
* 2024-01-13 02:14:36 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pZfttxBuL8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-13 02:14:36 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-14 02:13:06 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-14 02:13:06 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-14 02:13:06 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-14 02:13:06 (4251) [[32mINFO[0m] 
* 2024-01-14 02:13:06 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-14 02:13:06 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-14 02:13:06 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-14 02:13:06 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-14 02:13:06 (4281) [[32mINFO[0m] 
* 2024-01-14 02:13:06 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-14 02:13:06 (4251) [[32mINFO[0m] 
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m] 
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m] 
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m] 
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m] 
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m] 
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m] 
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m] 
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]         or
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m] 
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]         compromise:
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m] 
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m] 
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-14 02:13:39 (4281) [[32mINFO[0m] 
* 2024-01-14 02:13:39 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-14 02:13:39 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-14 02:13:39 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-14 02:13:39 (4251) [[32mINFO[0m] 
* 2024-01-14 02:13:39 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-14 02:13:41 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-14 02:13:41 (4281) [[32mINFO[0m] 
* 2024-01-14 02:13:44 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-14 02:13:44 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-14 02:13:44 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-14 02:13:45 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-14 02:13:45 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Hbri7HyxBY/ea_profile.json
* 2024-01-14 02:13:50 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Hbri7HyxBY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-14 02:13:50 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-15 02:12:36 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-15 02:12:36 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-15 02:12:36 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-15 02:12:36 (4251) [[32mINFO[0m] 
* 2024-01-15 02:12:36 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-15 02:12:36 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-15 02:12:36 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-15 02:12:36 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-15 02:12:36 (4281) [[32mINFO[0m] 
* 2024-01-15 02:12:36 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-15 02:12:36 (4251) [[32mINFO[0m] 
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]         or
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]         compromise:
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m] 
* 2024-01-15 02:12:40 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-15 02:12:41 (4281) [[32mINFO[0m] 
* 2024-01-15 02:12:41 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-15 02:12:41 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-15 02:12:41 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-15 02:12:41 (4251) [[32mINFO[0m] 
* 2024-01-15 02:12:41 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-15 02:12:42 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-15 02:12:42 (4281) [[32mINFO[0m] 
* 2024-01-15 02:13:14 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-15 02:13:14 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-15 02:13:14 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-15 02:13:15 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-15 02:13:15 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BRI2GeDUU4/ea_profile.json
* 2024-01-15 02:13:20 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BRI2GeDUU4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-15 02:13:20 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-16 02:12:35 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-16 02:12:35 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-16 02:12:35 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-16 02:12:35 (4251) [[32mINFO[0m] 
* 2024-01-16 02:12:35 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-16 02:12:35 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-16 02:12:35 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-16 02:12:35 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-16 02:12:35 (4281) [[32mINFO[0m] 
* 2024-01-16 02:12:35 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-16 02:12:35 (4251) [[32mINFO[0m] 
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]         or
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]         compromise:
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m] 
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-16 02:12:39 (4281) [[32mINFO[0m] 
* 2024-01-16 02:12:39 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-16 02:12:39 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-16 02:12:39 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-16 02:12:39 (4251) [[32mINFO[0m] 
* 2024-01-16 02:12:39 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-16 02:12:40 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-16 02:12:40 (4281) [[32mINFO[0m] 
* 2024-01-16 02:12:44 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-16 02:12:44 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-16 02:12:44 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-16 02:12:44 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-16 02:12:44 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gpHwe0x5Ov/ea_profile.json
* 2024-01-16 02:12:49 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gpHwe0x5Ov/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-16 02:12:49 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-17 02:12:29 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-17 02:12:29 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-17 02:12:29 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-17 02:12:29 (4251) [[32mINFO[0m] 
* 2024-01-17 02:12:29 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-17 02:12:30 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-17 02:12:30 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-17 02:12:30 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-17 02:12:30 (4281) [[32mINFO[0m] 
* 2024-01-17 02:12:30 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-17 02:12:30 (4251) [[32mINFO[0m] 
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m] 
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m] 
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m] 
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m] 
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m] 
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m] 
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m] 
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]         or
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m] 
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]         compromise:
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m] 
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m] 
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-17 02:12:34 (4281) [[32mINFO[0m] 
* 2024-01-17 02:12:34 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-17 02:12:34 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-17 02:12:34 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-17 02:12:34 (4251) [[32mINFO[0m] 
* 2024-01-17 02:12:34 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-17 02:12:35 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-17 02:12:35 (4281) [[32mINFO[0m] 
* 2024-01-17 02:12:39 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-17 02:12:39 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-17 02:12:39 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-17 02:12:39 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-17 02:12:40 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cXlxzl2zSl/ea_profile.json
* 2024-01-17 02:12:46 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cXlxzl2zSl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-17 02:12:46 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-18 02:12:33 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-18 02:12:33 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-18 02:12:33 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-18 02:12:33 (4251) [[32mINFO[0m] 
* 2024-01-18 02:12:33 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-18 02:12:33 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-18 02:12:33 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-18 02:12:33 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-18 02:12:33 (4281) [[32mINFO[0m] 
* 2024-01-18 02:12:33 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-18 02:12:33 (4251) [[32mINFO[0m] 
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]         or
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]         compromise:
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m] 
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-18 02:12:37 (4281) [[32mINFO[0m] 
* 2024-01-18 02:12:37 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-18 02:12:37 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-18 02:12:37 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-18 02:12:37 (4251) [[32mINFO[0m] 
* 2024-01-18 02:12:37 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-18 02:12:39 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-18 02:12:39 (4281) [[32mINFO[0m] 
* 2024-01-18 02:12:42 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-18 02:12:42 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-18 02:12:42 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-18 02:12:43 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-18 02:12:43 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SSk4tmut7Z/ea_profile.json
* 2024-01-18 02:12:49 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SSk4tmut7Z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-18 02:12:49 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-19 02:12:37 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-19 02:12:37 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-19 02:12:37 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-19 02:12:37 (4251) [[32mINFO[0m] 
* 2024-01-19 02:12:37 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-19 02:12:38 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-19 02:12:38 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-19 02:12:38 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-19 02:12:38 (4281) [[32mINFO[0m] 
* 2024-01-19 02:12:38 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-19 02:12:38 (4251) [[32mINFO[0m] 
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m] 
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m] 
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m] 
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m] 
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m] 
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m] 
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m] 
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]         or
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m] 
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]         compromise:
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m] 
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m] 
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-19 02:12:44 (4281) [[32mINFO[0m] 
* 2024-01-19 02:12:44 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-19 02:12:44 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-19 02:12:44 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-19 02:12:44 (4251) [[32mINFO[0m] 
* 2024-01-19 02:12:44 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-19 02:12:46 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-19 02:12:46 (4281) [[32mINFO[0m] 
* 2024-01-19 02:12:49 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-19 02:12:49 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-19 02:12:49 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-19 02:12:50 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-19 02:12:51 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jgawu1szYw/ea_profile.json
* 2024-01-19 02:12:57 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jgawu1szYw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-19 02:12:57 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-19 15:48:10 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-19 15:48:10 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-19 15:48:10 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-19 15:48:10 (4251) [[32mINFO[0m] 
* 2024-01-19 15:48:10 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-19 15:48:10 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-19 15:48:10 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-19 15:48:10 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-19 15:48:10 (4281) [[32mINFO[0m] 
* 2024-01-19 15:48:10 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-19 15:48:10 (4251) [[32mINFO[0m] 
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m] 
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m] 
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m] 
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m] 
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m] 
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m] 
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m] 
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]         or
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m] 
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]         compromise:
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m] 
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m] 
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-19 15:48:43 (4281) [[32mINFO[0m] 
* 2024-01-19 15:48:43 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-19 15:48:43 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-19 15:48:43 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-19 15:48:43 (4251) [[32mINFO[0m] 
* 2024-01-19 15:48:43 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-19 15:48:45 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-19 15:48:45 (4281) [[32mINFO[0m] 
* 2024-01-19 15:48:48 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-19 15:48:48 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-19 15:48:48 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-19 15:48:49 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-19 15:48:49 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pDA0Z_eM2D/ea_profile.json
* 2024-01-19 15:48:55 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pDA0Z_eM2D/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-19 15:48:55 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-20 02:13:07 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-20 02:13:07 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-20 02:13:07 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-20 02:13:07 (4251) [[32mINFO[0m] 
* 2024-01-20 02:13:08 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-20 02:13:08 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-20 02:13:08 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-20 02:13:08 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-20 02:13:08 (4281) [[32mINFO[0m] 
* 2024-01-20 02:13:08 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-20 02:13:08 (4251) [[32mINFO[0m] 
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m] 
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m] 
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m] 
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m] 
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m] 
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m] 
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m] 
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]         or
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m] 
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]         compromise:
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m] 
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m] 
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-20 02:13:41 (4281) [[32mINFO[0m] 
* 2024-01-20 02:13:41 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-20 02:13:41 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-20 02:13:41 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-20 02:13:41 (4251) [[32mINFO[0m] 
* 2024-01-20 02:13:41 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-20 02:13:42 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-20 02:13:42 (4281) [[32mINFO[0m] 
* 2024-01-20 02:13:46 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-20 02:13:46 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-20 02:13:46 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-20 02:13:46 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-20 02:13:46 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_DXNZEZtoy/ea_profile.json
* 2024-01-20 02:13:52 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_DXNZEZtoy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-20 02:13:52 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-21 02:13:07 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-21 02:13:07 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-21 02:13:07 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-21 02:13:07 (4251) [[32mINFO[0m] 
* 2024-01-21 02:13:07 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-21 02:13:08 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-21 02:13:08 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-21 02:13:08 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-21 02:13:08 (4281) [[32mINFO[0m] 
* 2024-01-21 02:13:08 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-21 02:13:08 (4251) [[32mINFO[0m] 
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m] 
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m] 
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m] 
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m] 
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m] 
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m] 
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m] 
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]         or
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m] 
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]         compromise:
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m] 
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m] 
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-21 02:13:12 (4281) [[32mINFO[0m] 
* 2024-01-21 02:13:12 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-21 02:13:12 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-21 02:13:12 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-21 02:13:12 (4251) [[32mINFO[0m] 
* 2024-01-21 02:13:12 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-21 02:13:13 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-21 02:13:13 (4281) [[32mINFO[0m] 
* 2024-01-21 02:13:45 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-21 02:13:45 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-21 02:13:45 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-21 02:13:45 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-21 02:13:45 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iRhWShK7bk/ea_profile.json
* 2024-01-21 02:13:51 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iRhWShK7bk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-21 02:13:51 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-22 02:12:31 (577) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-22 02:12:31 (1774) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-22 02:12:31 (4250) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-22 02:12:31 (4251) [[32mINFO[0m] 
* 2024-01-22 02:12:31 (4264) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-22 02:12:31 (4264) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-22 02:12:31 (4264) [[32mINFO[0m]               : epel extras updates
* 2024-01-22 02:12:31 (4264) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-22 02:12:31 (4281) [[32mINFO[0m] 
* 2024-01-22 02:12:31 (4250) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-22 02:12:31 (4251) [[32mINFO[0m] 
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m] 
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m] 
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m] 
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m] 
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m] 
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m] 
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m] 
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]         or
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m] 
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]         compromise:
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m] 
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m] 
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-22 02:12:35 (4281) [[32mINFO[0m] 
* 2024-01-22 02:12:35 (1781) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-22 02:12:35 (1795) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-22 02:12:35 (4250) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-22 02:12:35 (4251) [[32mINFO[0m] 
* 2024-01-22 02:12:35 (4264) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-22 02:12:36 (4264) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-22 02:12:36 (4281) [[32mINFO[0m] 
* 2024-01-22 02:12:40 (1633) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-22 02:12:40 (1634) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-22 02:12:40 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-22 02:12:40 (823) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-22 02:12:40 (2292) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WRO4F7VZ9z/ea_profile.json
* 2024-01-22 02:12:47 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WRO4F7VZ9z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294.
* 2024-01-22 02:12:47 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-23 02:12:36 (645) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-23 02:12:36 (1842) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-23 02:12:36 (4318) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-23 02:12:36 (4319) [[32mINFO[0m] 
* 2024-01-23 02:12:37 (4332) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-23 02:12:37 (4332) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-23 02:12:37 (4332) [[32mINFO[0m]               : epel extras updates
* 2024-01-23 02:12:37 (4332) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-23 02:12:37 (4349) [[32mINFO[0m] 
* 2024-01-23 02:12:37 (4318) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-23 02:12:37 (4319) [[32mINFO[0m] 
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m] 
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m] 
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m] 
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m] 
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m] 
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m] 
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m] 
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]         or
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m] 
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]         compromise:
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m] 
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m] 
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-23 02:12:42 (4349) [[32mINFO[0m] 
* 2024-01-23 02:12:42 (1849) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-23 02:12:42 (1863) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-23 02:12:42 (4318) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-23 02:12:42 (4319) [[32mINFO[0m] 
* 2024-01-23 02:12:42 (4332) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-23 02:12:43 (4332) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-23 02:12:43 (4349) [[32mINFO[0m] 
* 2024-01-23 02:12:47 (1701) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-23 02:12:47 (1702) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-23 02:12:47 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-23 02:12:47 (891) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-23 02:12:47 (2360) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NPOHhOE2uK/ea_profile.json
* 2024-01-23 02:12:53 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NPOHhOE2uK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2362.
* 2024-01-23 02:12:53 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-24 02:12:33 (645) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-24 02:12:33 (1842) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-24 02:12:33 (4318) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-24 02:12:33 (4319) [[32mINFO[0m] 
* 2024-01-24 02:12:33 (4332) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-24 02:12:33 (4332) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-24 02:12:33 (4332) [[32mINFO[0m]               : epel extras updates
* 2024-01-24 02:12:33 (4332) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-24 02:12:33 (4349) [[32mINFO[0m] 
* 2024-01-24 02:12:33 (4318) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-24 02:12:33 (4319) [[32mINFO[0m] 
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m] 
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m] 
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m] 
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m] 
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m] 
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m] 
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m] 
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]         or
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m] 
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]         compromise:
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m] 
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m] 
* 2024-01-24 02:13:05 (4332) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-24 02:13:05 (4349) [[32mINFO[0m] 
* 2024-01-24 02:13:05 (1849) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-24 02:13:05 (1863) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-24 02:13:05 (4318) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-24 02:13:05 (4319) [[32mINFO[0m] 
* 2024-01-24 02:13:06 (4332) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-24 02:13:07 (4332) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-24 02:13:07 (4349) [[32mINFO[0m] 
* 2024-01-24 02:13:11 (1701) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-24 02:13:11 (1702) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-24 02:13:11 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-24 02:13:11 (891) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-24 02:13:11 (2360) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hry2NMd8Og/ea_profile.json
* 2024-01-24 02:13:20 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hry2NMd8Og/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2362.
* 2024-01-24 02:13:20 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-25 02:16:46 (645) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-25 02:16:46 (1842) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-25 02:16:46 (4318) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-25 02:16:46 (4319) [[32mINFO[0m] 
* 2024-01-25 02:16:46 (4332) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-25 02:16:46 (4332) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-25 02:16:46 (4332) [[32mINFO[0m]               : epel extras updates
* 2024-01-25 02:16:46 (4332) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-25 02:16:46 (4349) [[32mINFO[0m] 
* 2024-01-25 02:16:46 (4318) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-25 02:16:46 (4319) [[32mINFO[0m] 
* 2024-01-25 02:17:17 (4332) [[32mINFO[0m] 
* 2024-01-25 02:17:17 (4332) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-25 02:17:17 (4349) [[32mINFO[0m] 
* 2024-01-25 02:17:17 (1849) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-25 02:17:17 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-25 02:17:40 (891) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-25 02:17:42 (2360) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JuhVNbms3P/ea_profile.json
* 2024-01-25 02:17:43 (2383) [[32mINFO[0m] Backed up EA4 profile to /tmp/JuhVNbms3P/ea_profile.json
* 2024-01-25 02:17:44 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2024-01-25 02:17:46 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.90.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.102.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2024-01-25 02:17:47 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-26 02:12:47 (645) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-26 02:12:47 (1842) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-26 02:12:47 (4321) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-26 02:12:47 (4322) [[32mINFO[0m] 
* 2024-01-26 02:12:47 (4335) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-26 02:12:47 (4335) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-26 02:12:47 (4335) [[32mINFO[0m]               : epel extras updates
* 2024-01-26 02:12:47 (4335) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-26 02:12:47 (4352) [[32mINFO[0m] 
* 2024-01-26 02:12:47 (4321) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-26 02:12:47 (4322) [[32mINFO[0m] 
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m] 
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m] 
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m] 
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m] 
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m] 
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m] 
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m] 
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]         or
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m] 
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]         compromise:
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m] 
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m] 
* 2024-01-26 02:12:53 (4335) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-26 02:12:53 (4352) [[32mINFO[0m] 
* 2024-01-26 02:12:53 (1849) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-26 02:12:53 (1863) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-26 02:12:53 (4321) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-26 02:12:53 (4322) [[32mINFO[0m] 
* 2024-01-26 02:12:54 (4335) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-26 02:12:55 (4335) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-26 02:12:55 (4352) [[32mINFO[0m] 
* 2024-01-26 02:13:27 (1701) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-26 02:13:27 (1702) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-26 02:13:27 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-26 02:13:28 (891) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-26 02:13:28 (2359) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/COoJ3XCbFN/ea_profile.json
* 2024-01-26 02:13:36 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/COoJ3XCbFN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-01-26 02:13:36 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-26 15:47:44 (645) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-26 15:47:44 (1842) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-26 15:47:44 (4321) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-26 15:47:44 (4322) [[32mINFO[0m] 
* 2024-01-26 15:47:44 (4335) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-26 15:47:45 (4335) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-26 15:47:45 (4335) [[32mINFO[0m]               : epel extras updates
* 2024-01-26 15:47:45 (4335) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-26 15:47:45 (4352) [[32mINFO[0m] 
* 2024-01-26 15:47:45 (4321) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-26 15:47:45 (4322) [[32mINFO[0m] 
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m] 
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m] 
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m] 
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m] 
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m] 
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m] 
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m] 
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]         or
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m] 
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]         compromise:
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m] 
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m] 
* 2024-01-26 15:47:52 (4335) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-26 15:47:52 (4352) [[32mINFO[0m] 
* 2024-01-26 15:47:52 (1849) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-26 15:47:52 (1863) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-26 15:47:52 (4321) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-26 15:47:52 (4322) [[32mINFO[0m] 
* 2024-01-26 15:47:53 (4335) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-26 15:47:54 (4335) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-26 15:47:54 (4352) [[32mINFO[0m] 
* 2024-01-26 15:48:02 (1701) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-26 15:48:02 (1702) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-26 15:48:02 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-26 15:48:02 (891) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-26 15:48:02 (2359) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qeHQK8EHpe/ea_profile.json
* 2024-01-26 15:48:18 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qeHQK8EHpe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-01-26 15:48:18 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-27 02:13:09 (645) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-27 02:13:09 (1842) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-27 02:13:09 (4321) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-27 02:13:09 (4322) [[32mINFO[0m] 
* 2024-01-27 02:13:09 (4335) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-27 02:13:09 (4335) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-27 02:13:09 (4335) [[32mINFO[0m]               : epel extras updates
* 2024-01-27 02:13:09 (4335) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-27 02:13:09 (4352) [[32mINFO[0m] 
* 2024-01-27 02:13:09 (4321) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-27 02:13:09 (4322) [[32mINFO[0m] 
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m] 
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m] 
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m] 
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m] 
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m] 
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m] 
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m] 
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]         or
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m] 
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]         compromise:
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m] 
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m] 
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-27 02:13:15 (4352) [[32mINFO[0m] 
* 2024-01-27 02:13:15 (1849) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-27 02:13:15 (1863) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-27 02:13:15 (4321) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-27 02:13:15 (4322) [[32mINFO[0m] 
* 2024-01-27 02:13:15 (4335) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-27 02:13:16 (4335) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-27 02:13:16 (4352) [[32mINFO[0m] 
* 2024-01-27 02:13:21 (1701) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-27 02:13:21 (1702) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-27 02:13:21 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-27 02:13:22 (891) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-27 02:13:22 (2359) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/E4nA3M4Ye7/ea_profile.json
* 2024-01-27 02:13:29 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/E4nA3M4Ye7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-01-27 02:13:29 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-28 02:13:12 (645) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-28 02:13:12 (1842) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-28 02:13:12 (4321) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-28 02:13:12 (4322) [[32mINFO[0m] 
* 2024-01-28 02:13:13 (4335) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-28 02:13:13 (4335) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-28 02:13:13 (4335) [[32mINFO[0m]               : epel extras updates
* 2024-01-28 02:13:13 (4335) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-28 02:13:13 (4352) [[32mINFO[0m] 
* 2024-01-28 02:13:13 (4321) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-28 02:13:13 (4322) [[32mINFO[0m] 
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m] 
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m] 
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m] 
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m] 
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m] 
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m] 
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m] 
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]         or
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m] 
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]         compromise:
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m] 
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m] 
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-28 02:13:17 (4352) [[32mINFO[0m] 
* 2024-01-28 02:13:17 (1849) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-28 02:13:17 (1863) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-28 02:13:17 (4321) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-28 02:13:17 (4322) [[32mINFO[0m] 
* 2024-01-28 02:13:17 (4335) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-28 02:13:18 (4335) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-28 02:13:18 (4352) [[32mINFO[0m] 
* 2024-01-28 02:13:21 (1701) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-28 02:13:21 (1702) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-28 02:13:21 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-28 02:13:22 (891) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-28 02:13:23 (2359) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5yHNAlO4IQ/ea_profile.json
* 2024-01-28 02:13:28 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5yHNAlO4IQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-01-28 02:13:28 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-29 02:12:36 (645) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-29 02:12:36 (1842) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-29 02:12:36 (4321) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-29 02:12:36 (4322) [[32mINFO[0m] 
* 2024-01-29 02:12:36 (4335) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-29 02:12:36 (4335) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-29 02:12:36 (4335) [[32mINFO[0m]               : epel extras updates
* 2024-01-29 02:12:36 (4335) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-29 02:12:36 (4352) [[32mINFO[0m] 
* 2024-01-29 02:12:36 (4321) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-29 02:12:36 (4322) [[32mINFO[0m] 
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m] 
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m] 
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m] 
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m] 
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m] 
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m] 
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m] 
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]         or
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m] 
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]         compromise:
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m] 
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m] 
* 2024-01-29 02:12:40 (4335) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-29 02:12:40 (4352) [[32mINFO[0m] 
* 2024-01-29 02:12:40 (1849) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-29 02:12:40 (1863) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-29 02:12:40 (4321) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-29 02:12:40 (4322) [[32mINFO[0m] 
* 2024-01-29 02:12:41 (4335) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-29 02:12:42 (4335) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-29 02:12:42 (4352) [[32mINFO[0m] 
* 2024-01-29 02:12:45 (1701) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-29 02:12:45 (1702) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-29 02:12:46 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-29 02:12:46 (891) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-29 02:12:47 (2359) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mLKTDmcc0A/ea_profile.json
* 2024-01-29 02:12:52 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mLKTDmcc0A/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-01-29 02:12:52 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-31 02:15:55 (645) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-01-31 02:15:55 (1842) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-01-31 02:15:55 (4321) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-01-31 02:15:55 (4322) [[32mINFO[0m] 
* 2024-01-31 02:15:55 (4335) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-31 02:15:55 (4335) [[32mINFO[0m] Existing lock /var/run/yum.pid: another copy is running as pid 26253.
* 2024-01-31 02:15:55 (4335) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-31 02:15:55 (4335) [[32mINFO[0m]   The other application is: yum
* 2024-01-31 02:15:55 (4335) [[32mINFO[0m]     Memory :  25 M RSS (353 MB VSZ)
* 2024-01-31 02:15:55 (4335) [[32mINFO[0m]     Started: Wed Jan 31 02:15:53 2024 - 00:02 ago
* 2024-01-31 02:15:55 (4335) [[32mINFO[0m]     State  : Sleeping, pid: 26253
* 2024-01-31 02:15:57 (4335) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-01-31 02:15:57 (4335) [[32mINFO[0m]               : epel extras updates
* 2024-01-31 02:15:57 (4335) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-01-31 02:15:57 (4335) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-01-31 02:15:57 (4352) [[32mINFO[0m] 
* 2024-01-31 02:15:57 (4321) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-01-31 02:15:57 (4322) [[32mINFO[0m] 
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m] 
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m] 
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m] 
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m] 
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m] 
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m] 
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m] 
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]         or
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m] 
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]         compromise:
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m] 
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m] 
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-31 02:16:01 (4352) [[32mINFO[0m] 
* 2024-01-31 02:16:01 (1849) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-31 02:16:01 (1863) [[32mINFO[0m] Checking /scripts/sysup
* 2024-01-31 02:16:01 (4321) [[32mINFO[0m] Running: /scripts/sysup
* 2024-01-31 02:16:01 (4322) [[32mINFO[0m] 
* 2024-01-31 02:16:01 (4335) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-31 02:16:03 (4335) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-01-31 02:16:03 (4352) [[32mINFO[0m] 
* 2024-01-31 02:16:06 (1701) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-01-31 02:16:06 (1702) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-01-31 02:16:06 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-01-31 02:16:07 (891) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-31 02:16:07 (2359) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aW0g2Yi9fC/ea_profile.json
* 2024-01-31 02:16:13 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aW0g2Yi9fC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-01-31 02:16:13 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-01 02:12:32 (645) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-01 02:12:32 (1842) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-01 02:12:32 (4321) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-01 02:12:32 (4322) [[32mINFO[0m] 
* 2024-02-01 02:12:32 (4335) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-01 02:12:32 (4335) [[32mINFO[0m] Existing lock /var/run/yum.pid: another copy is running as pid 16594.
* 2024-02-01 02:12:32 (4335) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-01 02:12:32 (4335) [[32mINFO[0m]   The other application is: yum
* 2024-02-01 02:12:32 (4335) [[32mINFO[0m]     Memory :  25 M RSS (353 MB VSZ)
* 2024-02-01 02:12:32 (4335) [[32mINFO[0m]     Started: Thu Feb  1 02:12:30 2024 - 00:02 ago
* 2024-02-01 02:12:32 (4335) [[32mINFO[0m]     State  : Sleeping, pid: 16594
* 2024-02-01 02:12:34 (4335) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-01 02:12:34 (4335) [[32mINFO[0m]               : epel extras updates
* 2024-02-01 02:12:34 (4335) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-02-01 02:12:34 (4335) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-01 02:12:34 (4352) [[32mINFO[0m] 
* 2024-02-01 02:12:34 (4321) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-01 02:12:34 (4322) [[32mINFO[0m] 
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m] 
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m] 
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m] 
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m] 
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m] 
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m] 
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m] 
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]         or
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m] 
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]         compromise:
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m] 
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m] 
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-01 02:12:38 (4352) [[32mINFO[0m] 
* 2024-02-01 02:12:38 (1849) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-01 02:12:38 (1863) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-01 02:12:38 (4321) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-01 02:12:38 (4322) [[32mINFO[0m] 
* 2024-02-01 02:12:38 (4335) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-01 02:12:40 (4335) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-01 02:12:40 (4352) [[32mINFO[0m] 
* 2024-02-01 02:12:43 (1701) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-01 02:12:43 (1702) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-01 02:12:43 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-01 02:12:44 (891) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-01 02:12:44 (2359) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dsoKBCYII1/ea_profile.json
* 2024-02-01 02:12:53 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dsoKBCYII1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-02-01 02:12:53 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-02 02:12:33 (645) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-02 02:12:33 (1842) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-02 02:12:33 (4321) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-02 02:12:33 (4322) [[32mINFO[0m] 
* 2024-02-02 02:12:33 (4335) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-02 02:12:33 (4335) [[32mINFO[0m] Existing lock /var/run/yum.pid: another copy is running as pid 9517.
* 2024-02-02 02:12:33 (4335) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-02 02:12:33 (4335) [[32mINFO[0m]   The other application is: yum
* 2024-02-02 02:12:33 (4335) [[32mINFO[0m]     Memory :  25 M RSS (352 MB VSZ)
* 2024-02-02 02:12:33 (4335) [[32mINFO[0m]     Started: Fri Feb  2 02:12:32 2024 - 00:01 ago
* 2024-02-02 02:12:33 (4335) [[32mINFO[0m]     State  : Sleeping, pid: 9517
* 2024-02-02 02:12:35 (4335) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-02 02:12:35 (4335) [[32mINFO[0m]   The other application is: yum
* 2024-02-02 02:12:35 (4335) [[32mINFO[0m]     Memory :  25 M RSS (353 MB VSZ)
* 2024-02-02 02:12:35 (4335) [[32mINFO[0m]     Started: Fri Feb  2 02:12:32 2024 - 00:03 ago
* 2024-02-02 02:12:35 (4335) [[32mINFO[0m]     State  : Sleeping, pid: 9517
* 2024-02-02 02:12:37 (4335) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-02 02:12:37 (4335) [[32mINFO[0m]               : epel extras updates
* 2024-02-02 02:12:37 (4335) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-02-02 02:12:37 (4335) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-02 02:12:37 (4352) [[32mINFO[0m] 
* 2024-02-02 02:12:37 (4321) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-02 02:12:37 (4322) [[32mINFO[0m] 
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m] 
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m] 
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m] 
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m] 
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m] 
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m] 
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m] 
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]         or
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m] 
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]         compromise:
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m] 
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m] 
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-02 02:12:41 (4352) [[32mINFO[0m] 
* 2024-02-02 02:12:41 (1849) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-02 02:12:41 (1863) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-02 02:12:41 (4321) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-02 02:12:41 (4322) [[32mINFO[0m] 
* 2024-02-02 02:12:41 (4335) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-02 02:12:42 (4335) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-02 02:12:42 (4352) [[32mINFO[0m] 
* 2024-02-02 02:12:46 (1701) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-02 02:12:46 (1702) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-02 02:12:46 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-02 02:12:46 (891) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-02 02:12:47 (2359) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pEt_z6BZIn/ea_profile.json
* 2024-02-02 02:12:54 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pEt_z6BZIn/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-02-02 02:12:54 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-02 15:46:50 (645) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-02 15:46:50 (1842) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-02 15:46:50 (4321) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-02 15:46:50 (4322) [[32mINFO[0m] 
* 2024-02-02 15:46:50 (4335) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-02 15:46:51 (4335) [[32mINFO[0m] Existing lock /var/run/yum.pid: another copy is running as pid 27129.
* 2024-02-02 15:46:51 (4335) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-02 15:46:51 (4335) [[32mINFO[0m]   The other application is: yum
* 2024-02-02 15:46:51 (4335) [[32mINFO[0m]     Memory :  25 M RSS (352 MB VSZ)
* 2024-02-02 15:46:51 (4335) [[32mINFO[0m]     Started: Fri Feb  2 15:46:49 2024 - 00:02 ago
* 2024-02-02 15:46:51 (4335) [[32mINFO[0m]     State  : Sleeping, pid: 27129
* 2024-02-02 15:46:53 (4335) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-02 15:46:53 (4335) [[32mINFO[0m]   The other application is: yum
* 2024-02-02 15:46:53 (4335) [[32mINFO[0m]     Memory :  25 M RSS (353 MB VSZ)
* 2024-02-02 15:46:53 (4335) [[32mINFO[0m]     Started: Fri Feb  2 15:46:49 2024 - 00:04 ago
* 2024-02-02 15:46:53 (4335) [[32mINFO[0m]     State  : Sleeping, pid: 27129
* 2024-02-02 15:46:55 (4335) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-02 15:46:55 (4335) [[32mINFO[0m]   The other application is: yum
* 2024-02-02 15:46:55 (4335) [[32mINFO[0m]     Memory :  25 M RSS (353 MB VSZ)
* 2024-02-02 15:46:55 (4335) [[32mINFO[0m]     Started: Fri Feb  2 15:46:49 2024 - 00:06 ago
* 2024-02-02 15:46:55 (4335) [[32mINFO[0m]     State  : Sleeping, pid: 27129
* 2024-02-02 15:46:57 (4335) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-02 15:46:57 (4335) [[32mINFO[0m]               : epel extras updates
* 2024-02-02 15:46:57 (4335) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-02-02 15:46:57 (4335) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-02 15:46:57 (4352) [[32mINFO[0m] 
* 2024-02-02 15:46:57 (4321) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-02 15:46:57 (4322) [[32mINFO[0m] 
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m] 
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m] 
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m] 
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m] 
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m] 
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m] 
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m] 
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]         or
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m] 
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]         compromise:
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m] 
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m] 
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-02 15:47:00 (4352) [[32mINFO[0m] 
* 2024-02-02 15:47:00 (1849) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-02 15:47:00 (1863) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-02 15:47:00 (4321) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-02 15:47:00 (4322) [[32mINFO[0m] 
* 2024-02-02 15:47:00 (4335) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-02 15:47:01 (4335) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-02 15:47:01 (4352) [[32mINFO[0m] 
* 2024-02-02 15:47:05 (1701) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-02 15:47:05 (1702) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-02 15:47:05 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-02 15:47:06 (891) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-02 15:47:06 (2359) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/j5oLOmRQLC/ea_profile.json
* 2024-02-02 15:47:13 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/j5oLOmRQLC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-02-02 15:47:13 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-03 02:13:40 (645) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-03 02:13:40 (1842) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-03 02:13:40 (4321) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-03 02:13:40 (4322) [[32mINFO[0m] 
* 2024-02-03 02:13:41 (4335) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-03 02:13:41 (4335) [[32mINFO[0m] Existing lock /var/run/yum.pid: another copy is running as pid 30187.
* 2024-02-03 02:13:41 (4335) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-03 02:13:41 (4335) [[32mINFO[0m]   The other application is: yum
* 2024-02-03 02:13:41 (4335) [[32mINFO[0m]     Memory :  25 M RSS (353 MB VSZ)
* 2024-02-03 02:13:41 (4335) [[32mINFO[0m]     Started: Sat Feb  3 02:13:39 2024 - 00:02 ago
* 2024-02-03 02:13:41 (4335) [[32mINFO[0m]     State  : Sleeping, pid: 30187
* 2024-02-03 02:13:43 (4335) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-03 02:13:43 (4335) [[32mINFO[0m]   The other application is: yum
* 2024-02-03 02:13:43 (4335) [[32mINFO[0m]     Memory :  25 M RSS (353 MB VSZ)
* 2024-02-03 02:13:43 (4335) [[32mINFO[0m]     Started: Sat Feb  3 02:13:39 2024 - 00:04 ago
* 2024-02-03 02:13:43 (4335) [[32mINFO[0m]     State  : Sleeping, pid: 30187
* 2024-02-03 02:13:45 (4335) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-03 02:13:45 (4335) [[32mINFO[0m]   The other application is: yum
* 2024-02-03 02:13:45 (4335) [[32mINFO[0m]     Memory :  25 M RSS (353 MB VSZ)
* 2024-02-03 02:13:45 (4335) [[32mINFO[0m]     Started: Sat Feb  3 02:13:39 2024 - 00:06 ago
* 2024-02-03 02:13:45 (4335) [[32mINFO[0m]     State  : Sleeping, pid: 30187
* 2024-02-03 02:13:47 (4335) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-03 02:13:47 (4335) [[32mINFO[0m]   The other application is: yum
* 2024-02-03 02:13:47 (4335) [[32mINFO[0m]     Memory :  25 M RSS (353 MB VSZ)
* 2024-02-03 02:13:47 (4335) [[32mINFO[0m]     Started: Sat Feb  3 02:13:39 2024 - 00:08 ago
* 2024-02-03 02:13:47 (4335) [[32mINFO[0m]     State  : Sleeping, pid: 30187
* 2024-02-03 02:13:49 (4335) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-03 02:13:49 (4335) [[32mINFO[0m]   The other application is: yum
* 2024-02-03 02:13:49 (4335) [[32mINFO[0m]     Memory :  25 M RSS (353 MB VSZ)
* 2024-02-03 02:13:49 (4335) [[32mINFO[0m]     Started: Sat Feb  3 02:13:39 2024 - 00:10 ago
* 2024-02-03 02:13:49 (4335) [[32mINFO[0m]     State  : Sleeping, pid: 30187
* 2024-02-03 02:13:51 (4335) [[32mINFO[0m] Existing lock /var/run/yum.pid: another copy is running as pid 30202.
* 2024-02-03 02:13:51 (4335) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-03 02:13:51 (4335) [[32mINFO[0m]   The other application is: yum
* 2024-02-03 02:13:51 (4335) [[32mINFO[0m]     Memory :  25 M RSS (352 MB VSZ)
* 2024-02-03 02:13:51 (4335) [[32mINFO[0m]     Started: Sat Feb  3 02:13:50 2024 - 00:01 ago
* 2024-02-03 02:13:51 (4335) [[32mINFO[0m]     State  : Sleeping, pid: 30202
* 2024-02-03 02:13:53 (4335) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-03 02:13:53 (4335) [[32mINFO[0m]   The other application is: yum
* 2024-02-03 02:13:53 (4335) [[32mINFO[0m]     Memory :  25 M RSS (353 MB VSZ)
* 2024-02-03 02:13:53 (4335) [[32mINFO[0m]     Started: Sat Feb  3 02:13:50 2024 - 00:03 ago
* 2024-02-03 02:13:53 (4335) [[32mINFO[0m]     State  : Sleeping, pid: 30202
* 2024-02-03 02:13:55 (4335) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-03 02:13:55 (4335) [[32mINFO[0m]               : epel extras updates
* 2024-02-03 02:13:55 (4335) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-02-03 02:13:55 (4335) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-03 02:13:55 (4352) [[32mINFO[0m] 
* 2024-02-03 02:13:55 (4321) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-03 02:13:55 (4322) [[32mINFO[0m] 
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m] 
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m] 
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m] 
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m] 
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m] 
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m] 
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m] 
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]         or
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m] 
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]         compromise:
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m] 
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m] 
* 2024-02-03 02:13:58 (4335) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-03 02:13:58 (4352) [[32mINFO[0m] 
* 2024-02-03 02:13:58 (1849) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-03 02:13:58 (1863) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-03 02:13:58 (4321) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-03 02:13:58 (4322) [[32mINFO[0m] 
* 2024-02-03 02:13:59 (4335) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-03 02:14:00 (4335) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-03 02:14:00 (4352) [[32mINFO[0m] 
* 2024-02-03 02:14:03 (1701) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-03 02:14:03 (1702) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-03 02:14:03 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-03 02:14:03 (891) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-03 02:14:04 (2359) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tyd6wZNDtI/ea_profile.json
* 2024-02-03 02:14:10 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tyd6wZNDtI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-02-03 02:14:10 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-04 02:13:03 (645) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-04 02:13:03 (1842) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-04 02:13:03 (4321) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-04 02:13:03 (4322) [[32mINFO[0m] 
* 2024-02-04 02:13:04 (4335) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-04 02:13:04 (4335) [[32mINFO[0m] Existing lock /var/run/yum.pid: another copy is running as pid 1450.
* 2024-02-04 02:13:04 (4335) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-04 02:13:04 (4335) [[32mINFO[0m]   The other application is: yum
* 2024-02-04 02:13:04 (4335) [[32mINFO[0m]     Memory :  25 M RSS (352 MB VSZ)
* 2024-02-04 02:13:04 (4335) [[32mINFO[0m]     Started: Sun Feb  4 02:13:01 2024 - 00:03 ago
* 2024-02-04 02:13:04 (4335) [[32mINFO[0m]     State  : Sleeping, pid: 1450
* 2024-02-04 02:13:06 (4335) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-04 02:13:06 (4335) [[32mINFO[0m]               : epel extras updates
* 2024-02-04 02:13:06 (4335) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-02-04 02:13:06 (4335) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-04 02:13:06 (4352) [[32mINFO[0m] 
* 2024-02-04 02:13:06 (4321) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-04 02:13:06 (4322) [[32mINFO[0m] 
* 2024-02-04 02:13:09 (4335) [[32mINFO[0m] 
* 2024-02-04 02:13:09 (4335) [[32mINFO[0m] 
* 2024-02-04 02:13:09 (4335) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-04 02:13:09 (4335) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-04 02:13:09 (4335) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-04 02:13:09 (4335) [[32mINFO[0m] 
* 2024-02-04 02:13:09 (4335) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-04 02:13:09 (4335) [[32mINFO[0m] 
* 2024-02-04 02:13:09 (4335) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m] 
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m] 
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m] 
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m]         or
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m] 
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m]         compromise:
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m] 
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m] 
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-04 02:13:10 (4352) [[32mINFO[0m] 
* 2024-02-04 02:13:10 (1849) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-04 02:13:10 (1863) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-04 02:13:10 (4321) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-04 02:13:10 (4322) [[32mINFO[0m] 
* 2024-02-04 02:13:10 (4335) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-04 02:13:11 (4335) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-04 02:13:11 (4352) [[32mINFO[0m] 
* 2024-02-04 02:13:14 (1701) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-04 02:13:14 (1702) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-04 02:13:14 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-04 02:13:15 (891) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-04 02:13:17 (2359) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/f9CIoMyFOa/ea_profile.json
* 2024-02-04 02:13:23 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/f9CIoMyFOa/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-02-04 02:13:23 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-05 02:12:32 (645) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-05 02:12:32 (1842) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-05 02:12:32 (4321) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-05 02:12:32 (4322) [[32mINFO[0m] 
* 2024-02-05 02:12:32 (4335) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-05 02:12:32 (4335) [[32mINFO[0m] Existing lock /var/run/yum.pid: another copy is running as pid 7509.
* 2024-02-05 02:12:32 (4335) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-05 02:12:32 (4335) [[32mINFO[0m]   The other application is: yum
* 2024-02-05 02:12:32 (4335) [[32mINFO[0m]     Memory :  25 M RSS (352 MB VSZ)
* 2024-02-05 02:12:32 (4335) [[32mINFO[0m]     Started: Mon Feb  5 02:12:30 2024 - 00:02 ago
* 2024-02-05 02:12:32 (4335) [[32mINFO[0m]     State  : Sleeping, pid: 7509
* 2024-02-05 02:12:34 (4335) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-05 02:12:34 (4335) [[32mINFO[0m]   The other application is: yum
* 2024-02-05 02:12:34 (4335) [[32mINFO[0m]     Memory :  25 M RSS (353 MB VSZ)
* 2024-02-05 02:12:34 (4335) [[32mINFO[0m]     Started: Mon Feb  5 02:12:30 2024 - 00:04 ago
* 2024-02-05 02:12:34 (4335) [[32mINFO[0m]     State  : Sleeping, pid: 7509
* 2024-02-05 02:12:36 (4335) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-05 02:12:36 (4335) [[32mINFO[0m]               : epel extras updates
* 2024-02-05 02:12:36 (4335) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-02-05 02:12:36 (4335) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-05 02:12:36 (4352) [[32mINFO[0m] 
* 2024-02-05 02:12:36 (4321) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-05 02:12:36 (4322) [[32mINFO[0m] 
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m] 
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m] 
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m] 
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m] 
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m] 
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m] 
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m] 
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]         or
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m] 
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]         compromise:
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m] 
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m] 
* 2024-02-05 02:12:40 (4335) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-05 02:12:40 (4352) [[32mINFO[0m] 
* 2024-02-05 02:12:40 (1849) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-05 02:12:40 (1863) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-05 02:12:40 (4321) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-05 02:12:40 (4322) [[32mINFO[0m] 
* 2024-02-05 02:12:41 (4335) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-05 02:12:42 (4335) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-05 02:12:42 (4352) [[32mINFO[0m] 
* 2024-02-05 02:12:46 (1701) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-05 02:12:46 (1702) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-05 02:12:46 (161) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-05 02:12:47 (891) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-05 02:12:47 (2359) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/96mzGgtH7d/ea_profile.json
* 2024-02-05 02:12:52 (307) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/96mzGgtH7d/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2361.
* 2024-02-05 02:12:52 (268) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-06 02:12:32 (647) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-06 02:12:32 (1844) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-06 02:12:32 (4415) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-06 02:12:32 (4416) [[32mINFO[0m] 
* 2024-02-06 02:12:32 (4429) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-06 02:12:32 (4429) [[32mINFO[0m] Existing lock /var/run/yum.pid: another copy is running as pid 6211.
* 2024-02-06 02:12:32 (4429) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-06 02:12:32 (4429) [[32mINFO[0m]   The other application is: yum
* 2024-02-06 02:12:32 (4429) [[32mINFO[0m]     Memory :  25 M RSS (352 MB VSZ)
* 2024-02-06 02:12:32 (4429) [[32mINFO[0m]     Started: Tue Feb  6 02:12:30 2024 - 00:02 ago
* 2024-02-06 02:12:32 (4429) [[32mINFO[0m]     State  : Sleeping, pid: 6211
* 2024-02-06 02:12:34 (4429) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-06 02:12:34 (4429) [[32mINFO[0m]   The other application is: yum
* 2024-02-06 02:12:34 (4429) [[32mINFO[0m]     Memory :  25 M RSS (353 MB VSZ)
* 2024-02-06 02:12:34 (4429) [[32mINFO[0m]     Started: Tue Feb  6 02:12:30 2024 - 00:04 ago
* 2024-02-06 02:12:34 (4429) [[32mINFO[0m]     State  : Sleeping, pid: 6211
* 2024-02-06 02:12:36 (4429) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-06 02:12:36 (4429) [[32mINFO[0m]               : epel extras updates
* 2024-02-06 02:12:36 (4429) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-02-06 02:12:36 (4429) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-06 02:12:36 (4446) [[32mINFO[0m] 
* 2024-02-06 02:12:36 (4415) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-06 02:12:36 (4416) [[32mINFO[0m] 
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m] 
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m] 
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m] 
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m] 
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m] 
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m] 
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m] 
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]         or
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m] 
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]         compromise:
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m] 
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m] 
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-06 02:12:40 (4446) [[32mINFO[0m] 
* 2024-02-06 02:12:40 (1851) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-06 02:12:40 (1865) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-06 02:12:40 (4415) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-06 02:12:40 (4416) [[32mINFO[0m] 
* 2024-02-06 02:12:40 (4429) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-06 02:12:42 (4429) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-06 02:12:42 (4446) [[32mINFO[0m] 
* 2024-02-06 02:12:45 (1703) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-06 02:12:45 (1704) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-06 02:12:45 (162) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-06 02:12:45 (893) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-06 02:12:45 (2413) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LCbRjTaafV/ea_profile.json
* 2024-02-06 02:12:51 (309) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LCbRjTaafV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2415.
* 2024-02-06 02:12:51 (270) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-07 02:14:36 (647) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-07 02:14:36 (1844) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-07 02:14:36 (4415) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-07 02:14:36 (4416) [[32mINFO[0m] 
* 2024-02-07 02:14:36 (4429) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-07 02:14:36 (4429) [[32mINFO[0m] Existing lock /var/run/yum.pid: another copy is running as pid 4155.
* 2024-02-07 02:14:36 (4429) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-07 02:14:36 (4429) [[32mINFO[0m]   The other application is: yum
* 2024-02-07 02:14:36 (4429) [[32mINFO[0m]     Memory : 114 M RSS (4.5 GB VSZ)
* 2024-02-07 02:14:36 (4429) [[32mINFO[0m]     Started: Wed Feb  7 02:14:30 2024 - 00:06 ago
* 2024-02-07 02:14:36 (4429) [[32mINFO[0m]     State  : Running, pid: 4155
* 2024-02-07 02:14:38 (4429) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-07 02:14:38 (4429) [[32mINFO[0m]   The other application is: yum
* 2024-02-07 02:14:38 (4429) [[32mINFO[0m]     Memory : 104 M RSS (4.5 GB VSZ)
* 2024-02-07 02:14:38 (4429) [[32mINFO[0m]     Started: Wed Feb  7 02:14:30 2024 - 00:08 ago
* 2024-02-07 02:14:38 (4429) [[32mINFO[0m]     State  : Sleeping, pid: 4155
* 2024-02-07 02:14:40 (4429) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-07 02:14:40 (4429) [[32mINFO[0m]   The other application is: yum
* 2024-02-07 02:14:40 (4429) [[32mINFO[0m]     Memory : 108 M RSS (4.5 GB VSZ)
* 2024-02-07 02:14:40 (4429) [[32mINFO[0m]     Started: Wed Feb  7 02:14:30 2024 - 00:10 ago
* 2024-02-07 02:14:40 (4429) [[32mINFO[0m]     State  : Uninterruptible, pid: 4155
* 2024-02-07 02:14:42 (4429) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-07 02:14:42 (4429) [[32mINFO[0m]   The other application is: yum
* 2024-02-07 02:14:42 (4429) [[32mINFO[0m]     Memory : 127 M RSS (4.5 GB VSZ)
* 2024-02-07 02:14:42 (4429) [[32mINFO[0m]     Started: Wed Feb  7 02:14:30 2024 - 00:12 ago
* 2024-02-07 02:14:42 (4429) [[32mINFO[0m]     State  : Running, pid: 4155
* 2024-02-07 02:14:44 (4429) [[32mINFO[0m] Existing lock /var/run/yum.pid: another copy is running as pid 4367.
* 2024-02-07 02:14:44 (4429) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-07 02:14:44 (4429) [[32mINFO[0m]   The other application is: yum
* 2024-02-07 02:14:44 (4429) [[32mINFO[0m]     Memory :  25 M RSS (352 MB VSZ)
* 2024-02-07 02:14:44 (4429) [[32mINFO[0m]     Started: Wed Feb  7 02:14:43 2024 - 00:01 ago
* 2024-02-07 02:14:44 (4429) [[32mINFO[0m]     State  : Sleeping, pid: 4367
* 2024-02-07 02:14:46 (4429) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-07 02:14:46 (4429) [[32mINFO[0m]   The other application is: yum
* 2024-02-07 02:14:46 (4429) [[32mINFO[0m]     Memory :  45 M RSS (374 MB VSZ)
* 2024-02-07 02:14:46 (4429) [[32mINFO[0m]     Started: Wed Feb  7 02:14:43 2024 - 00:03 ago
* 2024-02-07 02:14:46 (4429) [[32mINFO[0m]     State  : Running, pid: 4367
* 2024-02-07 02:14:48 (4429) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-07 02:14:48 (4429) [[32mINFO[0m]   The other application is: yum
* 2024-02-07 02:14:48 (4429) [[32mINFO[0m]     Memory : 102 M RSS (439 MB VSZ)
* 2024-02-07 02:14:48 (4429) [[32mINFO[0m]     Started: Wed Feb  7 02:14:43 2024 - 00:05 ago
* 2024-02-07 02:14:48 (4429) [[32mINFO[0m]     State  : Running, pid: 4367
* 2024-02-07 02:14:50 (4429) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-07 02:14:50 (4429) [[32mINFO[0m]   The other application is: yum
* 2024-02-07 02:14:50 (4429) [[32mINFO[0m]     Memory : 107 M RSS (434 MB VSZ)
* 2024-02-07 02:14:50 (4429) [[32mINFO[0m]     Started: Wed Feb  7 02:14:43 2024 - 00:07 ago
* 2024-02-07 02:14:50 (4429) [[32mINFO[0m]     State  : Sleeping, pid: 4367
* 2024-02-07 02:14:52 (4429) [[32mINFO[0m] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-02-07 02:14:52 (4429) [[32mINFO[0m]   The other application is: yum
* 2024-02-07 02:14:52 (4429) [[32mINFO[0m]     Memory : 110 M RSS (438 MB VSZ)
* 2024-02-07 02:14:52 (4429) [[32mINFO[0m]     Started: Wed Feb  7 02:14:43 2024 - 00:09 ago
* 2024-02-07 02:14:52 (4429) [[32mINFO[0m]     State  : Sleeping, pid: 4367
* 2024-02-07 02:14:54 (4429) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-07 02:14:54 (4429) [[32mINFO[0m]               : epel extras updates
* 2024-02-07 02:14:54 (4429) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-02-07 02:14:54 (4429) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-07 02:14:54 (4446) [[32mINFO[0m] 
* 2024-02-07 02:14:54 (4415) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-07 02:14:54 (4416) [[32mINFO[0m] 
* 2024-02-07 02:15:27 (4429) [[32mINFO[0m] 
* 2024-02-07 02:15:27 (4429) [[32mINFO[0m] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-07 02:15:27 (4446) [[32mINFO[0m] 
* 2024-02-07 02:15:27 (1851) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-07 02:15:27 (162) [[33mWARN[0m] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-07 02:15:56 (893) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-07 02:15:57 (2413) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/f9sYp9n8Ki/ea_profile.json
* 2024-02-07 02:15:58 (2436) [[32mINFO[0m] Backed up EA4 profile to /tmp/f9sYp9n8Ki/ea_profile.json
* 2024-02-07 02:15:59 (162) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2024-02-07 02:16:01 (162) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.90.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.102.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2024-02-07 02:16:02 (270) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-08 02:16:37 (647) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-08 02:16:37 (1844) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-08 02:16:37 (4415) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-08 02:16:37 (4416) [[32mINFO[0m] 
* 2024-02-08 02:16:38 (4429) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-08 02:16:38 (4429) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-08 02:16:38 (4429) [[32mINFO[0m]               : epel extras updates
* 2024-02-08 02:16:38 (4429) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-08 02:16:38 (4446) [[32mINFO[0m] 
* 2024-02-08 02:16:38 (4415) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-08 02:16:38 (4416) [[32mINFO[0m] 
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m] 
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m] 
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m] 
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m] 
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m] 
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m] 
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m] 
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]         or
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m] 
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]         compromise:
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m] 
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m] 
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-08 02:16:42 (4446) [[32mINFO[0m] 
* 2024-02-08 02:16:42 (1851) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-08 02:16:42 (1865) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-08 02:16:42 (4415) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-08 02:16:42 (4416) [[32mINFO[0m] 
* 2024-02-08 02:16:42 (4429) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-08 02:16:44 (4429) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-08 02:16:44 (4446) [[32mINFO[0m] 
* 2024-02-08 02:16:48 (1703) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-08 02:16:48 (1704) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-08 02:16:48 (162) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-08 02:16:48 (893) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-08 02:16:49 (2413) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_nGqiPQGTV/ea_profile.json
* 2024-02-08 02:16:56 (309) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_nGqiPQGTV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2415.
* 2024-02-08 02:16:56 (270) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-09 02:12:42 (647) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-09 02:12:42 (1844) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-09 02:12:42 (4415) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-09 02:12:42 (4416) [[32mINFO[0m] 
* 2024-02-09 02:12:42 (4429) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-09 02:12:42 (4429) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-09 02:12:42 (4429) [[32mINFO[0m]               : epel extras updates
* 2024-02-09 02:12:42 (4429) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-09 02:12:42 (4446) [[32mINFO[0m] 
* 2024-02-09 02:12:42 (4415) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-09 02:12:42 (4416) [[32mINFO[0m] 
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m] 
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m] 
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m] 
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m] 
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m] 
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m] 
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m] 
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]         or
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m] 
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]         compromise:
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m] 
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m] 
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-09 02:12:46 (4446) [[32mINFO[0m] 
* 2024-02-09 02:12:46 (1851) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-09 02:12:46 (1865) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-09 02:12:46 (4415) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-09 02:12:46 (4416) [[32mINFO[0m] 
* 2024-02-09 02:12:46 (4429) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-09 02:12:48 (4429) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-09 02:12:48 (4446) [[32mINFO[0m] 
* 2024-02-09 02:13:20 (1703) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-09 02:13:20 (1704) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-09 02:13:20 (162) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-09 02:13:20 (893) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-09 02:13:20 (2413) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2dvW2Qness/ea_profile.json
* 2024-02-09 02:13:27 (309) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2dvW2Qness/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2415.
* 2024-02-09 02:13:27 (270) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-09 15:47:10 (647) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-09 15:47:10 (1844) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-09 15:47:10 (4415) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-09 15:47:10 (4416) [[32mINFO[0m] 
* 2024-02-09 15:47:10 (4429) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-09 15:47:11 (4429) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-09 15:47:11 (4429) [[32mINFO[0m]               : epel extras updates
* 2024-02-09 15:47:11 (4429) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-09 15:47:11 (4446) [[32mINFO[0m] 
* 2024-02-09 15:47:11 (4415) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-09 15:47:11 (4416) [[32mINFO[0m] 
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m] 
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m] 
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m] 
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m] 
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m] 
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m] 
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m] 
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]         or
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m] 
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]         compromise:
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m] 
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m] 
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-09 15:47:15 (4446) [[32mINFO[0m] 
* 2024-02-09 15:47:15 (1851) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-09 15:47:15 (1865) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-09 15:47:15 (4415) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-09 15:47:15 (4416) [[32mINFO[0m] 
* 2024-02-09 15:47:15 (4429) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-09 15:47:16 (4429) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-09 15:47:16 (4446) [[32mINFO[0m] 
* 2024-02-09 15:47:19 (1703) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-09 15:47:19 (1704) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-09 15:47:19 (162) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-09 15:47:19 (893) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-09 15:47:19 (2413) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OdaRDnrH1f/ea_profile.json
* 2024-02-09 15:47:28 (309) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OdaRDnrH1f/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2415.
* 2024-02-09 15:47:28 (270) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-10 02:13:05 (647) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-10 02:13:05 (1844) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-10 02:13:05 (4415) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-10 02:13:05 (4416) [[32mINFO[0m] 
* 2024-02-10 02:13:06 (4429) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-10 02:13:06 (4429) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-10 02:13:06 (4429) [[32mINFO[0m]               : epel extras updates
* 2024-02-10 02:13:06 (4429) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-10 02:13:06 (4446) [[32mINFO[0m] 
* 2024-02-10 02:13:06 (4415) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-10 02:13:06 (4416) [[32mINFO[0m] 
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m] 
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m] 
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m] 
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m] 
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m] 
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m] 
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m] 
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]         or
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m] 
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]         compromise:
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m] 
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m] 
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-10 02:13:10 (4446) [[32mINFO[0m] 
* 2024-02-10 02:13:10 (1851) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-10 02:13:10 (1865) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-10 02:13:10 (4415) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-10 02:13:10 (4416) [[32mINFO[0m] 
* 2024-02-10 02:13:10 (4429) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-10 02:13:12 (4429) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-10 02:13:12 (4446) [[32mINFO[0m] 
* 2024-02-10 02:13:15 (1703) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-10 02:13:15 (1704) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-10 02:13:15 (162) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-10 02:13:16 (893) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-10 02:13:16 (2413) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/g5TEx0vx2g/ea_profile.json
* 2024-02-10 02:13:23 (309) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/g5TEx0vx2g/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2415.
* 2024-02-10 02:13:23 (270) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-11 02:13:08 (647) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-11 02:13:08 (1844) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-11 02:13:08 (4415) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-11 02:13:08 (4416) [[32mINFO[0m] 
* 2024-02-11 02:13:09 (4429) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-11 02:13:09 (4429) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-11 02:13:09 (4429) [[32mINFO[0m]               : epel extras updates
* 2024-02-11 02:13:09 (4429) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-11 02:13:09 (4446) [[32mINFO[0m] 
* 2024-02-11 02:13:09 (4415) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-11 02:13:09 (4416) [[32mINFO[0m] 
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m] 
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m] 
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m] 
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m] 
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m] 
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m] 
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m] 
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]         or
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m] 
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]         compromise:
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m] 
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m] 
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-11 02:13:13 (4446) [[32mINFO[0m] 
* 2024-02-11 02:13:13 (1851) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-11 02:13:13 (1865) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-11 02:13:13 (4415) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-11 02:13:13 (4416) [[32mINFO[0m] 
* 2024-02-11 02:13:13 (4429) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-11 02:13:14 (4429) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-11 02:13:14 (4446) [[32mINFO[0m] 
* 2024-02-11 02:13:17 (1703) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-11 02:13:17 (1704) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-11 02:13:17 (162) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-11 02:13:18 (893) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-11 02:13:19 (2413) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IHaRHh3xv_/ea_profile.json
* 2024-02-11 02:13:25 (309) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IHaRHh3xv_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2415.
* 2024-02-11 02:13:25 (270) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-12 02:12:36 (647) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-12 02:12:36 (1844) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-12 02:12:36 (4415) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-12 02:12:36 (4416) [[32mINFO[0m] 
* 2024-02-12 02:12:36 (4429) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-12 02:12:36 (4429) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-12 02:12:36 (4429) [[32mINFO[0m]               : epel extras updates
* 2024-02-12 02:12:36 (4429) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-12 02:12:36 (4446) [[32mINFO[0m] 
* 2024-02-12 02:12:36 (4415) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-12 02:12:36 (4416) [[32mINFO[0m] 
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m] 
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m] 
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m] 
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m] 
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m] 
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m] 
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m] 
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]         or
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m] 
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]         compromise:
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m] 
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m] 
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-12 02:12:42 (4446) [[32mINFO[0m] 
* 2024-02-12 02:12:42 (1851) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-12 02:12:42 (1865) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-12 02:12:42 (4415) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-12 02:12:42 (4416) [[32mINFO[0m] 
* 2024-02-12 02:12:42 (4429) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-12 02:12:44 (4429) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-12 02:12:44 (4446) [[32mINFO[0m] 
* 2024-02-12 02:12:48 (1703) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-12 02:12:48 (1704) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-12 02:12:48 (162) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-12 02:12:48 (893) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-12 02:12:49 (2413) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iA__GR0AGl/ea_profile.json
* 2024-02-12 02:12:56 (309) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iA__GR0AGl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2415.
* 2024-02-12 02:12:56 (270) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-13 02:12:35 (648) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-13 02:12:35 (1845) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-13 02:12:35 (4462) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-13 02:12:35 (4463) [[32mINFO[0m] 
* 2024-02-13 02:12:36 (4476) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-13 02:12:36 (4476) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-13 02:12:36 (4476) [[32mINFO[0m]               : epel extras updates
* 2024-02-13 02:12:36 (4476) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-13 02:12:36 (4493) [[32mINFO[0m] 
* 2024-02-13 02:12:36 (4462) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-13 02:12:36 (4463) [[32mINFO[0m] 
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m] 
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m] 
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m] 
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m] 
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m] 
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m] 
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m] 
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]         or
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m] 
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]         compromise:
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m] 
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m] 
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-13 02:12:41 (4493) [[32mINFO[0m] 
* 2024-02-13 02:12:41 (1852) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-13 02:12:41 (1866) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-13 02:12:41 (4462) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-13 02:12:41 (4463) [[32mINFO[0m] 
* 2024-02-13 02:12:41 (4476) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-13 02:12:42 (4476) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-13 02:12:42 (4493) [[32mINFO[0m] 
* 2024-02-13 02:12:46 (1704) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-13 02:12:46 (1705) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-13 02:12:46 (163) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-13 02:12:46 (894) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-13 02:12:46 (2414) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jul1PE9Sxe/ea_profile.json
* 2024-02-13 02:13:20 (310) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jul1PE9Sxe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2416.
* 2024-02-13 02:13:20 (271) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-14 02:12:31 (648) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-14 02:12:31 (1845) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-14 02:12:31 (4462) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-14 02:12:31 (4463) [[32mINFO[0m] 
* 2024-02-14 02:12:31 (4476) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-14 02:12:31 (4476) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-14 02:12:31 (4476) [[32mINFO[0m]               : epel extras updates
* 2024-02-14 02:12:31 (4476) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-14 02:12:31 (4493) [[32mINFO[0m] 
* 2024-02-14 02:12:31 (4462) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-14 02:12:31 (4463) [[32mINFO[0m] 
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m] 
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m] 
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m] 
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m] 
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m] 
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m] 
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m] 
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]         or
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m] 
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]         compromise:
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m] 
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m] 
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-14 02:12:36 (4493) [[32mINFO[0m] 
* 2024-02-14 02:12:36 (1852) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-14 02:12:36 (1866) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-14 02:12:36 (4462) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-14 02:12:36 (4463) [[32mINFO[0m] 
* 2024-02-14 02:12:36 (4476) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-14 02:12:37 (4476) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-14 02:12:37 (4493) [[32mINFO[0m] 
* 2024-02-14 02:12:42 (1704) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-14 02:12:42 (1705) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-14 02:12:42 (163) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-14 02:12:43 (894) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-14 02:12:44 (2414) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iPRFSHmLpv/ea_profile.json
* 2024-02-14 02:12:50 (310) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iPRFSHmLpv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2416.
* 2024-02-14 02:12:50 (271) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-15 02:12:36 (648) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-15 02:12:36 (1845) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-15 02:12:36 (4462) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-15 02:12:36 (4463) [[32mINFO[0m] 
* 2024-02-15 02:12:36 (4476) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-15 02:12:36 (4476) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-15 02:12:36 (4476) [[32mINFO[0m]               : epel extras updates
* 2024-02-15 02:12:36 (4476) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-15 02:12:36 (4493) [[32mINFO[0m] 
* 2024-02-15 02:12:36 (4462) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-15 02:12:36 (4463) [[32mINFO[0m] 
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]         or
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]         compromise:
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-15 02:12:39 (4476) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-15 02:12:39 (4493) [[32mINFO[0m] 
* 2024-02-15 02:12:39 (1852) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-15 02:12:39 (1866) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-15 02:12:39 (4462) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-15 02:12:39 (4463) [[32mINFO[0m] 
* 2024-02-15 02:12:40 (4476) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-15 02:12:41 (4476) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-15 02:12:41 (4493) [[32mINFO[0m] 
* 2024-02-15 02:12:44 (1704) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-15 02:12:44 (1705) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-15 02:12:44 (163) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-15 02:12:44 (894) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-15 02:12:45 (2414) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/huw2QXyy03/ea_profile.json
* 2024-02-15 02:12:50 (310) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/huw2QXyy03/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2416.
* 2024-02-15 02:12:50 (271) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-16 02:12:33 (648) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-16 02:12:33 (1845) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-16 02:12:33 (4462) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-16 02:12:33 (4463) [[32mINFO[0m] 
* 2024-02-16 02:12:33 (4476) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-16 02:12:34 (4476) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-16 02:12:34 (4476) [[32mINFO[0m]               : epel extras updates
* 2024-02-16 02:12:34 (4476) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-16 02:12:34 (4493) [[32mINFO[0m] 
* 2024-02-16 02:12:34 (4462) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-16 02:12:34 (4463) [[32mINFO[0m] 
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m] 
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m] 
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m] 
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m] 
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m] 
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m] 
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m] 
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]         or
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m] 
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]         compromise:
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m] 
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m] 
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-16 02:13:06 (4493) [[32mINFO[0m] 
* 2024-02-16 02:13:06 (1852) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-16 02:13:06 (1866) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-16 02:13:06 (4462) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-16 02:13:06 (4463) [[32mINFO[0m] 
* 2024-02-16 02:13:06 (4476) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-16 02:13:08 (4476) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-16 02:13:08 (4493) [[32mINFO[0m] 
* 2024-02-16 02:13:11 (1704) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-16 02:13:11 (1705) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-16 02:13:11 (163) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-16 02:13:12 (894) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-16 02:13:12 (2414) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/D5dwcyRFye/ea_profile.json
* 2024-02-16 02:13:18 (310) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/D5dwcyRFye/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2416.
* 2024-02-16 02:13:18 (271) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-16 15:47:21 (648) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-16 15:47:21 (1845) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-16 15:47:21 (4462) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-16 15:47:21 (4463) [[32mINFO[0m] 
* 2024-02-16 15:47:21 (4476) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-16 15:47:21 (4476) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-16 15:47:21 (4476) [[32mINFO[0m]               : epel extras updates
* 2024-02-16 15:47:21 (4476) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-16 15:47:21 (4493) [[32mINFO[0m] 
* 2024-02-16 15:47:21 (4462) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-16 15:47:21 (4463) [[32mINFO[0m] 
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m] 
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m] 
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m] 
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m] 
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m] 
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m] 
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m] 
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]         or
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m] 
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]         compromise:
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m] 
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m] 
* 2024-02-16 15:47:26 (4476) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-16 15:47:26 (4493) [[32mINFO[0m] 
* 2024-02-16 15:47:26 (1852) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-16 15:47:26 (1866) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-16 15:47:26 (4462) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-16 15:47:26 (4463) [[32mINFO[0m] 
* 2024-02-16 15:47:27 (4476) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-16 15:47:28 (4476) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-16 15:47:28 (4493) [[32mINFO[0m] 
* 2024-02-16 15:48:00 (1704) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-16 15:48:00 (1705) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-16 15:48:00 (163) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-16 15:48:01 (894) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-16 15:48:01 (2414) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3Wrks4g6EV/ea_profile.json
* 2024-02-16 15:48:09 (310) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3Wrks4g6EV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2416.
* 2024-02-16 15:48:09 (271) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-17 02:13:10 (648) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-17 02:13:10 (1845) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-17 02:13:10 (4462) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-17 02:13:10 (4463) [[32mINFO[0m] 
* 2024-02-17 02:13:10 (4476) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-17 02:13:10 (4476) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-17 02:13:10 (4476) [[32mINFO[0m]               : epel extras updates
* 2024-02-17 02:13:10 (4476) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-17 02:13:10 (4493) [[32mINFO[0m] 
* 2024-02-17 02:13:10 (4462) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-17 02:13:10 (4463) [[32mINFO[0m] 
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m] 
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m] 
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m] 
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m] 
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m] 
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m] 
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m] 
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]         or
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m] 
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]         compromise:
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m] 
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m] 
* 2024-02-17 02:13:14 (4476) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-17 02:13:14 (4493) [[32mINFO[0m] 
* 2024-02-17 02:13:14 (1852) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-17 02:13:14 (1866) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-17 02:13:14 (4462) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-17 02:13:14 (4463) [[32mINFO[0m] 
* 2024-02-17 02:13:15 (4476) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-17 02:13:16 (4476) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-17 02:13:16 (4493) [[32mINFO[0m] 
* 2024-02-17 02:13:48 (1704) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-17 02:13:48 (1705) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-17 02:13:48 (163) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-17 02:13:48 (894) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-17 02:13:49 (2414) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rpcBOXZ6HT/ea_profile.json
* 2024-02-17 02:13:55 (310) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rpcBOXZ6HT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2416.
* 2024-02-17 02:13:55 (271) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-18 02:13:06 (648) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-18 02:13:06 (1845) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-18 02:13:06 (4462) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-18 02:13:06 (4463) [[32mINFO[0m] 
* 2024-02-18 02:13:07 (4476) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-18 02:13:07 (4476) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-18 02:13:08 (4476) [[32mINFO[0m]               : epel extras updates
* 2024-02-18 02:13:08 (4476) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-18 02:13:08 (4493) [[32mINFO[0m] 
* 2024-02-18 02:13:08 (4462) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-18 02:13:08 (4463) [[32mINFO[0m] 
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m] 
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m] 
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m] 
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m] 
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m] 
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m] 
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m] 
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]         or
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m] 
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]         compromise:
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m] 
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m] 
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-18 02:13:12 (4493) [[32mINFO[0m] 
* 2024-02-18 02:13:12 (1852) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-18 02:13:12 (1866) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-18 02:13:12 (4462) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-18 02:13:12 (4463) [[32mINFO[0m] 
* 2024-02-18 02:13:12 (4476) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-18 02:13:13 (4476) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-18 02:13:13 (4493) [[32mINFO[0m] 
* 2024-02-18 02:13:45 (1704) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-18 02:13:45 (1705) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-18 02:13:45 (163) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-18 02:13:46 (894) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-18 02:13:46 (2414) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nX9bAKfqRf/ea_profile.json
* 2024-02-18 02:13:53 (310) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nX9bAKfqRf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2416.
* 2024-02-18 02:13:53 (271) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-19 02:12:34 (648) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-19 02:12:34 (1845) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-19 02:12:34 (4462) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-19 02:12:34 (4463) [[32mINFO[0m] 
* 2024-02-19 02:12:35 (4476) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-19 02:12:35 (4476) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-19 02:12:35 (4476) [[32mINFO[0m]               : epel extras updates
* 2024-02-19 02:12:35 (4476) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-19 02:12:35 (4493) [[32mINFO[0m] 
* 2024-02-19 02:12:35 (4462) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-19 02:12:35 (4463) [[32mINFO[0m] 
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]         or
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]         compromise:
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m] 
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-19 02:12:39 (4493) [[32mINFO[0m] 
* 2024-02-19 02:12:39 (1852) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-19 02:12:39 (1866) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-19 02:12:39 (4462) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-19 02:12:39 (4463) [[32mINFO[0m] 
* 2024-02-19 02:12:39 (4476) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-19 02:12:40 (4476) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-19 02:12:40 (4493) [[32mINFO[0m] 
* 2024-02-19 02:12:44 (1704) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-19 02:12:44 (1705) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-19 02:12:44 (163) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-19 02:12:44 (894) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-19 02:12:44 (2414) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/W1Uf9igfyV/ea_profile.json
* 2024-02-19 02:12:51 (310) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/W1Uf9igfyV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2416.
* 2024-02-19 02:12:51 (271) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-20 02:12:38 (648) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-20 02:12:38 (1845) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-20 02:12:38 (4462) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-20 02:12:38 (4463) [[32mINFO[0m] 
* 2024-02-20 02:12:38 (4476) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-20 02:12:38 (4476) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-20 02:12:38 (4476) [[32mINFO[0m]               : epel extras updates
* 2024-02-20 02:12:38 (4476) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-20 02:12:38 (4493) [[32mINFO[0m] 
* 2024-02-20 02:12:38 (4462) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-20 02:12:38 (4463) [[32mINFO[0m] 
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m] 
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m] 
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m] 
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m] 
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m] 
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m] 
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m] 
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]         or
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m] 
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]         compromise:
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m] 
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m] 
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-20 02:12:42 (4493) [[32mINFO[0m] 
* 2024-02-20 02:12:42 (1852) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-20 02:12:42 (1866) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-20 02:12:42 (4462) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-20 02:12:42 (4463) [[32mINFO[0m] 
* 2024-02-20 02:12:42 (4476) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-20 02:12:43 (4476) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-20 02:12:43 (4493) [[32mINFO[0m] 
* 2024-02-20 02:13:16 (1704) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-20 02:13:16 (1705) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-20 02:13:16 (163) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-20 02:13:17 (894) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-20 02:13:17 (2414) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bKj1nXCzaX/ea_profile.json
* 2024-02-20 02:13:23 (310) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bKj1nXCzaX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2416.
* 2024-02-20 02:13:23 (271) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-21 02:12:35 (672) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-21 02:12:35 (1782) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-21 02:12:35 (4910) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-21 02:12:35 (4911) [[32mINFO[0m] 
* 2024-02-21 02:12:35 (4924) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-21 02:12:35 (4924) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-21 02:12:35 (4924) [[32mINFO[0m]               : epel extras updates
* 2024-02-21 02:12:35 (4924) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-21 02:12:35 (4941) [[32mINFO[0m] 
* 2024-02-21 02:12:35 (4910) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-21 02:12:35 (4911) [[32mINFO[0m] 
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m] 
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m] 
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m] 
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m] 
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m] 
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m] 
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m] 
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]         or
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m] 
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]         compromise:
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m] 
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m] 
* 2024-02-21 02:12:39 (4924) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-21 02:12:39 (4941) [[32mINFO[0m] 
* 2024-02-21 02:12:39 (1789) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-21 02:12:39 (1803) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-21 02:12:39 (4910) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-21 02:12:39 (4911) [[32mINFO[0m] 
* 2024-02-21 02:12:40 (4924) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-21 02:12:41 (4924) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-21 02:12:41 (4941) [[32mINFO[0m] 
* 2024-02-21 02:13:13 (1641) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-21 02:13:13 (1642) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-21 02:13:13 (170) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-21 02:13:14 (912) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-21 02:13:14 (2363) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_6MqwQL39O/ea_profile.json
* 2024-02-21 02:13:20 (317) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_6MqwQL39O/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2365.
* 2024-02-21 02:13:20 (278) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-22 02:15:19 (672) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-22 02:15:19 (1782) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-22 02:15:19 (4910) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-22 02:15:19 (4911) [[32mINFO[0m] 
* 2024-02-22 02:15:19 (4924) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-22 02:15:19 (4924) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-22 02:15:19 (4924) [[32mINFO[0m]               : epel extras updates
* 2024-02-22 02:15:19 (4924) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-22 02:15:19 (4941) [[32mINFO[0m] 
* 2024-02-22 02:15:19 (4910) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-22 02:15:19 (4911) [[32mINFO[0m] 
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m] 
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m] 
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m] 
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m] 
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m] 
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m] 
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m] 
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]         or
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m] 
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]         compromise:
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m] 
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m] 
* 2024-02-22 02:15:23 (4924) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-22 02:15:23 (4941) [[32mINFO[0m] 
* 2024-02-22 02:15:23 (1789) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-22 02:15:23 (1803) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-22 02:15:23 (4910) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-22 02:15:23 (4911) [[32mINFO[0m] 
* 2024-02-22 02:15:24 (4924) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-22 02:15:25 (4924) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-22 02:15:25 (4941) [[32mINFO[0m] 
* 2024-02-22 02:15:29 (1641) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-22 02:15:29 (1642) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-22 02:15:29 (170) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-22 02:15:30 (912) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-22 02:15:30 (2363) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XeTLUOAqsi/ea_profile.json
* 2024-02-22 02:15:36 (317) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XeTLUOAqsi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2365.
* 2024-02-22 02:15:36 (278) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-23 02:12:32 (672) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-23 02:12:32 (1782) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-23 02:12:32 (4910) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-23 02:12:32 (4911) [[32mINFO[0m] 
* 2024-02-23 02:12:32 (4924) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-23 02:12:32 (4924) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-23 02:12:32 (4924) [[32mINFO[0m]               : epel extras updates
* 2024-02-23 02:12:32 (4924) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-23 02:12:33 (4941) [[32mINFO[0m] 
* 2024-02-23 02:12:33 (4910) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-23 02:12:33 (4911) [[32mINFO[0m] 
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m] 
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m] 
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m] 
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m] 
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m] 
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m] 
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m] 
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]         or
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m] 
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]         compromise:
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m] 
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m] 
* 2024-02-23 02:12:36 (4924) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-23 02:12:36 (4941) [[32mINFO[0m] 
* 2024-02-23 02:12:36 (1789) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-23 02:12:36 (1803) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-23 02:12:36 (4910) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-23 02:12:36 (4911) [[32mINFO[0m] 
* 2024-02-23 02:12:37 (4924) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-23 02:12:38 (4924) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-23 02:12:38 (4941) [[32mINFO[0m] 
* 2024-02-23 02:12:41 (1641) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-23 02:12:41 (1642) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-23 02:12:41 (170) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-23 02:12:41 (912) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-23 02:12:41 (2363) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rSaAkFQH8U/ea_profile.json
* 2024-02-23 02:13:16 (317) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rSaAkFQH8U/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2365.
* 2024-02-23 02:13:16 (278) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-23 15:47:21 (672) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-23 15:47:21 (1782) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-23 15:47:21 (4910) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-23 15:47:21 (4911) [[32mINFO[0m] 
* 2024-02-23 15:47:21 (4924) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-23 15:47:21 (4924) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-23 15:47:21 (4924) [[32mINFO[0m]               : epel extras updates
* 2024-02-23 15:47:21 (4924) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-23 15:47:21 (4941) [[32mINFO[0m] 
* 2024-02-23 15:47:21 (4910) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-23 15:47:21 (4911) [[32mINFO[0m] 
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m] 
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m] 
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m] 
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m] 
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m] 
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m] 
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m] 
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]         or
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m] 
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]         compromise:
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m] 
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m] 
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-23 15:47:26 (4941) [[32mINFO[0m] 
* 2024-02-23 15:47:26 (1789) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-23 15:47:26 (1803) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-23 15:47:26 (4910) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-23 15:47:26 (4911) [[32mINFO[0m] 
* 2024-02-23 15:47:26 (4924) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-23 15:47:28 (4924) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-23 15:47:28 (4941) [[32mINFO[0m] 
* 2024-02-23 15:47:31 (1641) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-23 15:47:31 (1642) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-23 15:47:31 (170) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-23 15:47:32 (912) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-23 15:47:32 (2363) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7jmGrsEPpC/ea_profile.json
* 2024-02-23 15:47:39 (317) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7jmGrsEPpC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2365.
* 2024-02-23 15:47:39 (278) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-24 02:13:11 (672) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-24 02:13:11 (1782) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-24 02:13:11 (4910) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-24 02:13:11 (4911) [[32mINFO[0m] 
* 2024-02-24 02:13:11 (4924) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-24 02:13:11 (4924) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-24 02:13:11 (4924) [[32mINFO[0m]               : epel extras updates
* 2024-02-24 02:13:11 (4924) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-24 02:13:11 (4941) [[32mINFO[0m] 
* 2024-02-24 02:13:11 (4910) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-24 02:13:11 (4911) [[32mINFO[0m] 
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m] 
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m] 
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m] 
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m] 
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m] 
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m] 
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m] 
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]         or
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m] 
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]         compromise:
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m] 
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m] 
* 2024-02-24 02:13:44 (4924) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-24 02:13:44 (4941) [[32mINFO[0m] 
* 2024-02-24 02:13:44 (1789) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-24 02:13:44 (1803) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-24 02:13:44 (4910) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-24 02:13:44 (4911) [[32mINFO[0m] 
* 2024-02-24 02:13:45 (4924) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-24 02:13:46 (4924) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-24 02:13:46 (4941) [[32mINFO[0m] 
* 2024-02-24 02:13:49 (1641) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-24 02:13:49 (1642) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-24 02:13:49 (170) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-24 02:13:50 (912) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-24 02:13:50 (2363) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZxArOqu_1d/ea_profile.json
* 2024-02-24 02:13:56 (317) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZxArOqu_1d/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2365.
* 2024-02-24 02:13:56 (278) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-25 02:13:21 (672) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-25 02:13:21 (1782) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-25 02:13:21 (4910) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-25 02:13:21 (4911) [[32mINFO[0m] 
* 2024-02-25 02:13:22 (4924) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-25 02:13:22 (4924) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-25 02:13:22 (4924) [[32mINFO[0m]               : epel extras updates
* 2024-02-25 02:13:22 (4924) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-25 02:13:22 (4941) [[32mINFO[0m] 
* 2024-02-25 02:13:22 (4910) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-25 02:13:22 (4911) [[32mINFO[0m] 
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m] 
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m] 
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m] 
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m] 
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m] 
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m] 
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m] 
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]         or
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m] 
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]         compromise:
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m] 
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m] 
* 2024-02-25 02:13:26 (4924) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-25 02:13:26 (4941) [[32mINFO[0m] 
* 2024-02-25 02:13:26 (1789) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-25 02:13:26 (1803) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-25 02:13:26 (4910) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-25 02:13:26 (4911) [[32mINFO[0m] 
* 2024-02-25 02:13:27 (4924) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-25 02:13:28 (4924) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-25 02:13:28 (4941) [[32mINFO[0m] 
* 2024-02-25 02:13:32 (1641) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-25 02:13:32 (1642) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-25 02:13:32 (170) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-25 02:13:33 (912) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-25 02:13:33 (2363) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/W6DieCwt1e/ea_profile.json
* 2024-02-25 02:13:40 (317) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/W6DieCwt1e/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2365.
* 2024-02-25 02:13:40 (278) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-26 02:12:50 (672) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-26 02:12:50 (1782) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-26 02:12:50 (4910) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-26 02:12:50 (4911) [[32mINFO[0m] 
* 2024-02-26 02:12:50 (4924) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-26 02:12:51 (4924) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-26 02:12:51 (4924) [[32mINFO[0m]               : epel extras updates
* 2024-02-26 02:12:51 (4924) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-26 02:12:51 (4941) [[32mINFO[0m] 
* 2024-02-26 02:12:51 (4910) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-26 02:12:51 (4911) [[32mINFO[0m] 
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]         or
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]         compromise:
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-26 02:13:23 (4924) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-26 02:13:23 (4941) [[32mINFO[0m] 
* 2024-02-26 02:13:23 (1789) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-26 02:13:23 (1803) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-26 02:13:23 (4910) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-26 02:13:23 (4911) [[32mINFO[0m] 
* 2024-02-26 02:13:24 (4924) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-26 02:13:25 (4924) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-26 02:13:25 (4941) [[32mINFO[0m] 
* 2024-02-26 02:13:28 (1641) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-26 02:13:28 (1642) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-26 02:13:28 (170) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-26 02:13:29 (912) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-26 02:13:29 (2363) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zOyEkCfiNZ/ea_profile.json
* 2024-02-26 02:13:35 (317) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zOyEkCfiNZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2365.
* 2024-02-26 02:13:35 (278) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-27 02:12:47 (672) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-27 02:12:47 (1782) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-27 02:12:47 (4910) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-27 02:12:47 (4911) [[32mINFO[0m] 
* 2024-02-27 02:12:47 (4924) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-27 02:12:47 (4924) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-27 02:12:47 (4924) [[32mINFO[0m]               : epel extras updates
* 2024-02-27 02:12:47 (4924) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-27 02:12:47 (4941) [[32mINFO[0m] 
* 2024-02-27 02:12:47 (4910) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-27 02:12:47 (4911) [[32mINFO[0m] 
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m] 
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m] 
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m] 
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m] 
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m] 
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m] 
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m] 
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]         or
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m] 
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]         compromise:
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m] 
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m] 
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-27 02:13:20 (4941) [[32mINFO[0m] 
* 2024-02-27 02:13:20 (1789) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-27 02:13:20 (1803) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-27 02:13:20 (4910) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-27 02:13:20 (4911) [[32mINFO[0m] 
* 2024-02-27 02:13:20 (4924) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-27 02:13:21 (4924) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-27 02:13:21 (4941) [[32mINFO[0m] 
* 2024-02-27 02:13:25 (1641) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-27 02:13:25 (1642) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-27 02:13:25 (170) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-27 02:13:26 (912) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-27 02:13:26 (2363) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/thOapvxOWG/ea_profile.json
* 2024-02-27 02:13:32 (317) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/thOapvxOWG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2365.
* 2024-02-27 02:13:32 (278) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-28 02:12:50 (672) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-28 02:12:50 (1782) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-28 02:12:50 (4910) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-28 02:12:50 (4911) [[32mINFO[0m] 
* 2024-02-28 02:12:50 (4924) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-28 02:12:50 (4924) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-28 02:12:50 (4924) [[32mINFO[0m]               : epel extras updates
* 2024-02-28 02:12:50 (4924) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-28 02:12:50 (4941) [[32mINFO[0m] 
* 2024-02-28 02:12:50 (4910) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-28 02:12:50 (4911) [[32mINFO[0m] 
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]         or
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]         compromise:
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m] 
* 2024-02-28 02:13:23 (4924) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-28 02:13:23 (4941) [[32mINFO[0m] 
* 2024-02-28 02:13:23 (1789) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-28 02:13:23 (1803) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-28 02:13:23 (4910) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-28 02:13:23 (4911) [[32mINFO[0m] 
* 2024-02-28 02:13:24 (4924) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-28 02:13:25 (4924) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-28 02:13:25 (4941) [[32mINFO[0m] 
* 2024-02-28 02:13:29 (1641) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-28 02:13:29 (1642) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-28 02:13:29 (170) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-28 02:13:30 (912) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-28 02:13:30 (2363) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/50MeDHXWLa/ea_profile.json
* 2024-02-28 02:13:36 (317) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/50MeDHXWLa/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2365.
* 2024-02-28 02:13:36 (278) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-29 02:12:46 (718) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-02-29 02:12:46 (1828) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-02-29 02:12:46 (5104) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-02-29 02:12:46 (5105) [[32mINFO[0m] 
* 2024-02-29 02:12:46 (5118) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-29 02:12:46 (5118) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-02-29 02:12:46 (5118) [[32mINFO[0m]               : epel extras updates
* 2024-02-29 02:12:47 (5118) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-02-29 02:12:47 (5135) [[32mINFO[0m] 
* 2024-02-29 02:12:47 (5104) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-02-29 02:12:47 (5105) [[32mINFO[0m] 
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m] 
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m] 
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m] 
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m] 
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m] 
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m] 
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m] 
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]         or
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m] 
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]         compromise:
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m] 
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m] 
* 2024-02-29 02:13:20 (5118) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-29 02:13:21 (5135) [[32mINFO[0m] 
* 2024-02-29 02:13:21 (1835) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-29 02:13:21 (1849) [[32mINFO[0m] Checking /scripts/sysup
* 2024-02-29 02:13:21 (5104) [[32mINFO[0m] Running: /scripts/sysup
* 2024-02-29 02:13:21 (5105) [[32mINFO[0m] 
* 2024-02-29 02:13:21 (5118) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-29 02:13:22 (5118) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-02-29 02:13:22 (5135) [[32mINFO[0m] 
* 2024-02-29 02:13:26 (1687) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-02-29 02:13:26 (1688) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-02-29 02:13:26 (173) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-29 02:13:27 (958) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-29 02:13:28 (2465) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XH9HqH0QB6/ea_profile.json
* 2024-02-29 02:13:36 (322) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XH9HqH0QB6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2467.
* 2024-02-29 02:13:36 (283) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-01 02:12:52 (718) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-01 02:12:52 (1828) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-03-01 02:12:52 (5104) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-03-01 02:12:52 (5105) [[32mINFO[0m] 
* 2024-03-01 02:12:52 (5118) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-01 02:12:52 (5118) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-03-01 02:12:52 (5118) [[32mINFO[0m]               : epel extras updates
* 2024-03-01 02:12:53 (5118) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-03-01 02:12:53 (5135) [[32mINFO[0m] 
* 2024-03-01 02:12:53 (5104) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-03-01 02:12:53 (5105) [[32mINFO[0m] 
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m] 
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m] 
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m] 
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m] 
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m] 
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m] 
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m] 
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]         or
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m] 
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]         compromise:
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m] 
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m] 
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-01 02:13:26 (5135) [[32mINFO[0m] 
* 2024-03-01 02:13:26 (1835) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-01 02:13:26 (1849) [[32mINFO[0m] Checking /scripts/sysup
* 2024-03-01 02:13:26 (5104) [[32mINFO[0m] Running: /scripts/sysup
* 2024-03-01 02:13:26 (5105) [[32mINFO[0m] 
* 2024-03-01 02:13:26 (5118) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-01 02:13:27 (5118) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-03-01 02:13:27 (5135) [[32mINFO[0m] 
* 2024-03-01 02:13:31 (1687) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-01 02:13:31 (1688) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-01 02:13:31 (173) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-03-01 02:13:31 (958) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-01 02:13:31 (2465) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/t_DE0ahZf8/ea_profile.json
* 2024-03-01 02:13:37 (322) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/t_DE0ahZf8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2467.
* 2024-03-01 02:13:37 (283) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-01 15:47:11 (718) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-01 15:47:11 (1828) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-03-01 15:47:11 (5104) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-03-01 15:47:11 (5105) [[32mINFO[0m] 
* 2024-03-01 15:47:12 (5118) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-01 15:47:12 (5118) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-03-01 15:47:12 (5118) [[32mINFO[0m]               : epel extras updates
* 2024-03-01 15:47:12 (5118) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-03-01 15:47:12 (5135) [[32mINFO[0m] 
* 2024-03-01 15:47:12 (5104) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-03-01 15:47:12 (5105) [[32mINFO[0m] 
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m] 
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m] 
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m] 
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m] 
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m] 
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m] 
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m] 
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]         or
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m] 
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]         compromise:
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m] 
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m] 
* 2024-03-01 15:47:17 (5118) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-01 15:47:17 (5135) [[32mINFO[0m] 
* 2024-03-01 15:47:17 (1835) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-01 15:47:17 (1849) [[32mINFO[0m] Checking /scripts/sysup
* 2024-03-01 15:47:17 (5104) [[32mINFO[0m] Running: /scripts/sysup
* 2024-03-01 15:47:17 (5105) [[32mINFO[0m] 
* 2024-03-01 15:47:18 (5118) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-01 15:47:19 (5118) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-03-01 15:47:19 (5135) [[32mINFO[0m] 
* 2024-03-01 15:47:22 (1687) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-01 15:47:22 (1688) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-01 15:47:22 (173) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-03-01 15:47:23 (958) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-01 15:47:23 (2465) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/twzgGZ2lCi/ea_profile.json
* 2024-03-01 15:47:29 (322) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/twzgGZ2lCi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2467.
* 2024-03-01 15:47:29 (283) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-02 02:13:34 (718) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-02 02:13:34 (1828) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-03-02 02:13:34 (5104) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-03-02 02:13:34 (5105) [[32mINFO[0m] 
* 2024-03-02 02:13:34 (5118) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-02 02:13:34 (5118) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-03-02 02:13:34 (5118) [[32mINFO[0m]               : epel extras updates
* 2024-03-02 02:13:34 (5118) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-03-02 02:13:34 (5135) [[32mINFO[0m] 
* 2024-03-02 02:13:34 (5104) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-03-02 02:13:34 (5105) [[32mINFO[0m] 
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/cPAddons-c7-x86_64-mirrorlist error was
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m] 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')
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m] 
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m] 
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m] 
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m] 
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m] 
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m] 
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m] 
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]         or
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m] 
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]         compromise:
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m] 
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m] 
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m] Cannot find a valid baseurl for repo: cpanel-addons-production-feed/x86_64
* 2024-03-02 02:14:06 (5135) [[32mINFO[0m] 
* 2024-03-02 02:14:06 (1835) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-02 02:14:06 (1849) [[32mINFO[0m] Checking /scripts/sysup
* 2024-03-02 02:14:06 (5104) [[32mINFO[0m] Running: /scripts/sysup
* 2024-03-02 02:14:06 (5105) [[32mINFO[0m] 
* 2024-03-02 02:14:06 (5118) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-02 02:14:08 (5118) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-03-02 02:14:08 (5135) [[32mINFO[0m] 
* 2024-03-02 02:14:39 (1687) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-02 02:14:39 (1688) [[31mERROR[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/cPAddons-c7-x86_64-mirrorlist error was
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')


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: cpanel-addons-production-feed/x86_64
* 2024-03-02 02:14:39 (173) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-03-02 02:14:39 (958) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-02 02:14:39 (2465) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jPa3atL64n/ea_profile.json
* 2024-03-02 02:14:46 (322) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jPa3atL64n/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2467.
* 2024-03-02 02:14:46 (283) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-03 02:13:24 (718) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-03 02:13:24 (1828) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-03-03 02:13:24 (5104) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-03-03 02:13:24 (5105) [[32mINFO[0m] 
* 2024-03-03 02:13:25 (5118) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-03 02:13:25 (5118) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-03-03 02:13:25 (5118) [[32mINFO[0m]               : epel extras updates
* 2024-03-03 02:13:25 (5118) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-03-03 02:13:25 (5135) [[32mINFO[0m] 
* 2024-03-03 02:13:25 (5104) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-03-03 02:13:25 (5105) [[32mINFO[0m] 
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m] 
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m] 
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m] 
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m] 
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m] 
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m] 
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m] 
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]         or
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m] 
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]         compromise:
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m] 
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m] 
* 2024-03-03 02:13:29 (5118) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-03 02:13:29 (5135) [[32mINFO[0m] 
* 2024-03-03 02:13:29 (1835) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-03 02:13:29 (1849) [[32mINFO[0m] Checking /scripts/sysup
* 2024-03-03 02:13:29 (5104) [[32mINFO[0m] Running: /scripts/sysup
* 2024-03-03 02:13:29 (5105) [[32mINFO[0m] 
* 2024-03-03 02:13:30 (5118) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-03 02:13:31 (5118) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-03-03 02:13:31 (5135) [[32mINFO[0m] 
* 2024-03-03 02:13:35 (1687) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-03 02:13:35 (1688) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-03 02:13:35 (173) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-03-03 02:13:35 (958) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-03 02:13:35 (2465) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2YdPEth58G/ea_profile.json
* 2024-03-03 02:13:42 (322) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2YdPEth58G/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2467.
* 2024-03-03 02:13:42 (283) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-04 02:12:35 (718) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-04 02:12:35 (1828) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-03-04 02:12:35 (5104) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-03-04 02:12:35 (5105) [[32mINFO[0m] 
* 2024-03-04 02:12:35 (5118) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-04 02:12:35 (5118) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-03-04 02:12:35 (5118) [[32mINFO[0m]               : epel extras updates
* 2024-03-04 02:12:35 (5118) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-03-04 02:12:35 (5135) [[32mINFO[0m] 
* 2024-03-04 02:12:35 (5104) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-03-04 02:12:35 (5105) [[32mINFO[0m] 
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m] 
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m] 
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m] 
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m] 
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m] 
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m] 
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m] 
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]         or
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m] 
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]         compromise:
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m] 
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m] 
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-04 02:12:40 (5135) [[32mINFO[0m] 
* 2024-03-04 02:12:40 (1835) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-04 02:12:40 (1849) [[32mINFO[0m] Checking /scripts/sysup
* 2024-03-04 02:12:40 (5104) [[32mINFO[0m] Running: /scripts/sysup
* 2024-03-04 02:12:40 (5105) [[32mINFO[0m] 
* 2024-03-04 02:12:40 (5118) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-04 02:12:41 (5118) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-03-04 02:12:41 (5135) [[32mINFO[0m] 
* 2024-03-04 02:12:45 (1687) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-04 02:12:45 (1688) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-04 02:12:45 (173) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-03-04 02:12:46 (958) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-04 02:12:46 (2465) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EsIO7RMzTx/ea_profile.json
* 2024-03-04 02:12:52 (322) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EsIO7RMzTx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2467.
* 2024-03-04 02:12:52 (283) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-05 02:12:31 (718) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-05 02:12:31 (1828) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-03-05 02:12:31 (5104) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-03-05 02:12:31 (5105) [[32mINFO[0m] 
* 2024-03-05 02:12:32 (5118) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-05 02:12:32 (5118) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-03-05 02:12:32 (5118) [[32mINFO[0m]               : epel extras updates
* 2024-03-05 02:12:32 (5118) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-03-05 02:12:32 (5135) [[32mINFO[0m] 
* 2024-03-05 02:12:32 (5104) [[32mINFO[0m] Running: /usr/bin/yum check-update -q
* 2024-03-05 02:12:32 (5105) [[32mINFO[0m] 
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m] 
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m] 
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m] 
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m] 
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m] 
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m] 
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-03-05 02:12:35 (5118) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-03-05 02:12:36 (5118) [[32mINFO[0m] 
* 2024-03-05 02:12:36 (5118) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-03-05 02:12:36 (5118) [[32mINFO[0m]         or
* 2024-03-05 02:12:36 (5118) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-03-05 02:12:36 (5118) [[32mINFO[0m] 
* 2024-03-05 02:12:36 (5118) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-05 02:12:36 (5118) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-05 02:12:36 (5118) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-05 02:12:36 (5118) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-05 02:12:36 (5118) [[32mINFO[0m]         compromise:
* 2024-03-05 02:12:36 (5118) [[32mINFO[0m] 
* 2024-03-05 02:12:36 (5118) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-03-05 02:12:36 (5118) [[32mINFO[0m] 
* 2024-03-05 02:12:36 (5118) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-05 02:12:36 (5135) [[32mINFO[0m] 
* 2024-03-05 02:12:36 (1835) [[33mWARN[0m] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-05 02:12:36 (1849) [[32mINFO[0m] Checking /scripts/sysup
* 2024-03-05 02:12:36 (5104) [[32mINFO[0m] Running: /scripts/sysup
* 2024-03-05 02:12:36 (5105) [[32mINFO[0m] 
* 2024-03-05 02:12:36 (5118) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-05 02:12:37 (5118) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-03-05 02:12:37 (5135) [[32mINFO[0m] 
* 2024-03-05 02:12:40 (1687) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-05 02:12:40 (1688) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-05 02:12:40 (173) [[33mWARN[0m] *** Elevation Blocker detected: ***
yum is not stable
* 2024-03-05 02:12:40 (958) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-05 02:12:41 (2465) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NO4aSRNyp8/ea_profile.json
* 2024-03-05 02:13:14 (322) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NO4aSRNyp8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2467.
* 2024-03-05 02:13:14 (283) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-06 02:12:40 (735) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-06 02:12:40 (1896) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-03-06 02:12:40 (5195) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-03-06 02:12:40 (5196) [[32mINFO[0m] 
* 2024-03-06 02:12:40 (5209) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-06 02:12:40 (5209) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-03-06 02:12:40 (5209) [[32mINFO[0m]               : epel extras updates
* 2024-03-06 02:12:40 (5209) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-03-06 02:12:40 (5226) [[32mINFO[0m] 
* 2024-03-06 02:12:40 (5195) [[32mINFO[0m] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-06 02:12:40 (5196) [[32mINFO[0m] 
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m] 
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m] 
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m] 
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m] 
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m] 
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m] 
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m] 
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]         or
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m] 
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]         compromise:
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m] 
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m] 
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m] 
* 2024-03-06 02:12:44 (5226) [[32mINFO[0m] 
* 2024-03-06 02:12:44 (1940) [[32mINFO[0m] Checking /scripts/sysup
* 2024-03-06 02:12:44 (5195) [[32mINFO[0m] Running: /scripts/sysup
* 2024-03-06 02:12:44 (5196) [[32mINFO[0m] 
* 2024-03-06 02:12:44 (5209) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-06 02:12:45 (5209) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-03-06 02:12:45 (5226) [[32mINFO[0m] 
* 2024-03-06 02:12:48 (1700) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-06 02:12:48 (1701) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-06 02:12:49 (975) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-06 02:12:49 (2556) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/valgln5SQF/ea_profile.json
* 2024-03-06 02:13:23 (339) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/valgln5SQF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-06 02:13:23 (300) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-07 02:15:57 (735) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-07 02:15:57 (1896) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-03-07 02:15:57 (5195) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-03-07 02:15:57 (5196) [[32mINFO[0m] 
* 2024-03-07 02:15:58 (5209) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-07 02:15:58 (5209) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-03-07 02:15:58 (5209) [[32mINFO[0m]               : epel extras updates
* 2024-03-07 02:15:58 (5209) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-03-07 02:15:58 (5226) [[32mINFO[0m] 
* 2024-03-07 02:15:58 (5195) [[32mINFO[0m] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-07 02:15:58 (5196) [[32mINFO[0m] 
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m] 
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m] 
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m] 
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m] 
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m] 
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m] 
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m] 
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]         or
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m] 
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]         compromise:
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m] 
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m] 
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m] 
* 2024-03-07 02:16:02 (5226) [[32mINFO[0m] 
* 2024-03-07 02:16:02 (1940) [[32mINFO[0m] Checking /scripts/sysup
* 2024-03-07 02:16:02 (5195) [[32mINFO[0m] Running: /scripts/sysup
* 2024-03-07 02:16:02 (5196) [[32mINFO[0m] 
* 2024-03-07 02:16:02 (5209) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-07 02:16:03 (5209) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-03-07 02:16:03 (5226) [[32mINFO[0m] 
* 2024-03-07 02:16:07 (1700) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-07 02:16:07 (1701) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-07 02:16:07 (975) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-07 02:16:08 (2556) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/be6WwN348q/ea_profile.json
* 2024-03-07 02:16:14 (339) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/be6WwN348q/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-07 02:16:14 (300) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-08 02:12:31 (735) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-08 02:12:31 (1896) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-03-08 02:12:31 (5195) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-03-08 02:12:31 (5196) [[32mINFO[0m] 
* 2024-03-08 02:12:31 (5209) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-08 02:12:32 (5209) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-03-08 02:12:32 (5209) [[32mINFO[0m]               : epel extras updates
* 2024-03-08 02:12:32 (5209) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-03-08 02:12:32 (5226) [[32mINFO[0m] 
* 2024-03-08 02:12:32 (5195) [[32mINFO[0m] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-08 02:12:32 (5196) [[32mINFO[0m] 
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]         or
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]         compromise:
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-08 02:12:36 (5226) [[32mINFO[0m] 
* 2024-03-08 02:12:36 (1940) [[32mINFO[0m] Checking /scripts/sysup
* 2024-03-08 02:12:36 (5195) [[32mINFO[0m] Running: /scripts/sysup
* 2024-03-08 02:12:36 (5196) [[32mINFO[0m] 
* 2024-03-08 02:12:36 (5209) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-08 02:12:37 (5209) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-03-08 02:12:37 (5226) [[32mINFO[0m] 
* 2024-03-08 02:12:42 (1700) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-08 02:12:42 (1701) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-08 02:12:42 (975) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-08 02:12:42 (2556) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YzFrnoRfV1/ea_profile.json
* 2024-03-08 02:13:17 (339) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YzFrnoRfV1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-08 02:13:17 (300) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-08 15:46:41 (735) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-08 15:46:41 (1896) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-03-08 15:46:41 (5195) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-03-08 15:46:41 (5196) [[32mINFO[0m] 
* 2024-03-08 15:46:42 (5209) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-08 15:46:42 (5209) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-03-08 15:46:42 (5209) [[32mINFO[0m]               : epel extras updates
* 2024-03-08 15:46:42 (5209) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-03-08 15:46:42 (5226) [[32mINFO[0m] 
* 2024-03-08 15:46:42 (5195) [[32mINFO[0m] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-08 15:46:42 (5196) [[32mINFO[0m] 
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m] 
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m] 
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m] 
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m] 
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m] 
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m] 
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m] 
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]         or
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m] 
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]         compromise:
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m] 
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m] 
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m] 
* 2024-03-08 15:46:46 (5226) [[32mINFO[0m] 
* 2024-03-08 15:46:46 (1940) [[32mINFO[0m] Checking /scripts/sysup
* 2024-03-08 15:46:46 (5195) [[32mINFO[0m] Running: /scripts/sysup
* 2024-03-08 15:46:46 (5196) [[32mINFO[0m] 
* 2024-03-08 15:46:46 (5209) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-08 15:46:47 (5209) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-03-08 15:46:47 (5226) [[32mINFO[0m] 
* 2024-03-08 15:46:51 (1700) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-08 15:46:51 (1701) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-08 15:46:51 (975) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-08 15:46:51 (2556) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JHFdGc9bSN/ea_profile.json
* 2024-03-08 15:46:57 (339) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JHFdGc9bSN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-08 15:46:57 (300) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-09 02:13:07 (735) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-09 02:13:07 (1896) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-03-09 02:13:07 (5195) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-03-09 02:13:07 (5196) [[32mINFO[0m] 
* 2024-03-09 02:13:07 (5209) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-09 02:13:07 (5209) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-03-09 02:13:07 (5209) [[32mINFO[0m]               : epel extras updates
* 2024-03-09 02:13:07 (5209) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-03-09 02:13:07 (5226) [[32mINFO[0m] 
* 2024-03-09 02:13:07 (5195) [[32mINFO[0m] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-09 02:13:07 (5196) [[32mINFO[0m] 
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m] 
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m] 
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m] 
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m] 
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m] 
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m] 
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m] 
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]         or
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m] 
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]         compromise:
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m] 
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m] 
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-09 02:13:12 (5209) [[32mINFO[0m] 
* 2024-03-09 02:13:12 (5226) [[32mINFO[0m] 
* 2024-03-09 02:13:12 (1940) [[32mINFO[0m] Checking /scripts/sysup
* 2024-03-09 02:13:12 (5195) [[32mINFO[0m] Running: /scripts/sysup
* 2024-03-09 02:13:12 (5196) [[32mINFO[0m] 
* 2024-03-09 02:13:13 (5209) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-09 02:13:14 (5209) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-03-09 02:13:14 (5226) [[32mINFO[0m] 
* 2024-03-09 02:13:47 (1700) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-09 02:13:47 (1701) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-09 02:13:47 (975) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-09 02:13:47 (2556) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9uMkTpJZdN/ea_profile.json
* 2024-03-09 02:13:54 (339) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9uMkTpJZdN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-09 02:13:54 (300) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-10 02:15:40 (735) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-10 02:15:40 (1896) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-03-10 02:15:40 (5195) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-03-10 02:15:40 (5196) [[32mINFO[0m] 
* 2024-03-10 02:15:41 (5209) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-10 02:15:41 (5209) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-03-10 02:15:41 (5209) [[32mINFO[0m]               : epel extras updates
* 2024-03-10 02:15:41 (5209) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-03-10 02:15:41 (5226) [[32mINFO[0m] 
* 2024-03-10 02:15:41 (5195) [[32mINFO[0m] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-10 02:15:41 (5196) [[32mINFO[0m] 
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m] 
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m] 
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m] 
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m] 
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m] 
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m] 
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m] 
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]         or
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m] 
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]         compromise:
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m] 
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m] 
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-10 02:15:45 (5209) [[32mINFO[0m] 
* 2024-03-10 02:15:45 (5226) [[32mINFO[0m] 
* 2024-03-10 02:15:45 (1940) [[32mINFO[0m] Checking /scripts/sysup
* 2024-03-10 02:15:45 (5195) [[32mINFO[0m] Running: /scripts/sysup
* 2024-03-10 02:15:45 (5196) [[32mINFO[0m] 
* 2024-03-10 02:15:46 (5209) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-10 02:15:47 (5209) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-03-10 02:15:47 (5226) [[32mINFO[0m] 
* 2024-03-10 02:15:53 (1700) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-10 02:15:53 (1701) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-10 02:15:54 (975) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-10 02:15:55 (2556) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KFRixCIlc6/ea_profile.json
* 2024-03-10 02:16:00 (339) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KFRixCIlc6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-10 02:16:00 (300) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-11 02:12:35 (735) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-11 02:12:35 (1896) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-03-11 02:12:35 (5195) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-03-11 02:12:35 (5196) [[32mINFO[0m] 
* 2024-03-11 02:12:36 (5209) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-11 02:12:36 (5209) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-03-11 02:12:36 (5209) [[32mINFO[0m]               : epel extras updates
* 2024-03-11 02:12:36 (5209) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-03-11 02:12:36 (5226) [[32mINFO[0m] 
* 2024-03-11 02:12:36 (5195) [[32mINFO[0m] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-11 02:12:36 (5196) [[32mINFO[0m] 
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m] 
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m] 
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m] 
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m] 
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m] 
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m] 
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m] 
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]         or
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m] 
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]         compromise:
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m] 
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m] 
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-11 02:12:40 (5209) [[32mINFO[0m] 
* 2024-03-11 02:12:40 (5226) [[32mINFO[0m] 
* 2024-03-11 02:12:40 (1940) [[32mINFO[0m] Checking /scripts/sysup
* 2024-03-11 02:12:40 (5195) [[32mINFO[0m] Running: /scripts/sysup
* 2024-03-11 02:12:40 (5196) [[32mINFO[0m] 
* 2024-03-11 02:12:41 (5209) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-11 02:12:42 (5209) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-03-11 02:12:42 (5226) [[32mINFO[0m] 
* 2024-03-11 02:12:45 (1700) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-11 02:12:45 (1701) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-11 02:12:46 (975) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-11 02:12:47 (2556) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RrKBtuHYVU/ea_profile.json
* 2024-03-11 02:13:22 (339) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RrKBtuHYVU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-11 02:13:22 (300) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-12 02:12:33 (735) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-12 02:12:33 (1896) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-03-12 02:12:33 (5195) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-03-12 02:12:33 (5196) [[32mINFO[0m] 
* 2024-03-12 02:12:33 (5209) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-12 02:12:33 (5209) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-03-12 02:12:33 (5209) [[32mINFO[0m]               : epel extras updates
* 2024-03-12 02:12:33 (5209) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-03-12 02:12:33 (5226) [[32mINFO[0m] 
* 2024-03-12 02:12:33 (5195) [[32mINFO[0m] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-12 02:12:33 (5196) [[32mINFO[0m] 
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m] 
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m] 
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m] 
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m] 
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m] 
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m] 
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m] 
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]         or
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m] 
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]         compromise:
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m] 
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m] 
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m] 
* 2024-03-12 02:12:38 (5226) [[32mINFO[0m] 
* 2024-03-12 02:12:38 (1940) [[32mINFO[0m] Checking /scripts/sysup
* 2024-03-12 02:12:38 (5195) [[32mINFO[0m] Running: /scripts/sysup
* 2024-03-12 02:12:38 (5196) [[32mINFO[0m] 
* 2024-03-12 02:12:38 (5209) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-12 02:12:40 (5209) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-03-12 02:12:40 (5226) [[32mINFO[0m] 
* 2024-03-12 02:12:44 (1700) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-12 02:12:44 (1701) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-12 02:12:44 (975) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-12 02:12:44 (2556) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/nwYkwHOvCq/ea_profile.json
* 2024-03-12 02:13:19 (339) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/nwYkwHOvCq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-12 02:13:19 (300) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-13 02:12:30 (735) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-13 02:12:30 (1896) [[32mINFO[0m] Checking if your system is up to date: 
* 2024-03-13 02:12:30 (5195) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-03-13 02:12:30 (5196) [[32mINFO[0m] 
* 2024-03-13 02:12:31 (5209) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-13 02:12:31 (5209) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-03-13 02:12:31 (5209) [[32mINFO[0m]               : epel extras updates
* 2024-03-13 02:12:31 (5209) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-03-13 02:12:31 (5226) [[32mINFO[0m] 
* 2024-03-13 02:12:31 (5195) [[32mINFO[0m] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-13 02:12:31 (5196) [[32mINFO[0m] 
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]         or
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]         compromise:
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m] 
* 2024-03-13 02:12:36 (5226) [[32mINFO[0m] 
* 2024-03-13 02:12:36 (1940) [[32mINFO[0m] Checking /scripts/sysup
* 2024-03-13 02:12:36 (5195) [[32mINFO[0m] Running: /scripts/sysup
* 2024-03-13 02:12:36 (5196) [[32mINFO[0m] 
* 2024-03-13 02:12:36 (5209) [[32mINFO[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-13 02:12:37 (5209) [[32mINFO[0m]   All Needed Packages are already installed.
* 2024-03-13 02:12:37 (5226) [[32mINFO[0m] 
* 2024-03-13 02:12:42 (1700) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-13 02:12:42 (1701) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-13 02:12:42 (975) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-13 02:12:43 (2556) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/q5rBjjeX_R/ea_profile.json
* 2024-03-13 02:13:18 (339) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/q5rBjjeX_R/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2558.
* 2024-03-13 02:13:18 (300) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-14 02:12:35 (752) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-14 02:12:38 (1716) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-14 02:12:38 (1717) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-14 02:12:38 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-14 02:12:39 (2518) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tAhVu6qexV/ea_profile.json
* 2024-03-14 02:12:44 (340) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tAhVu6qexV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-14 02:12:44 (301) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-15 02:12:32 (752) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-15 02:12:35 (1716) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-15 02:12:35 (1717) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-15 02:12:35 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-15 02:12:35 (2518) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YlljSsI8bW/ea_profile.json
* 2024-03-15 02:12:42 (340) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YlljSsI8bW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-15 02:12:42 (301) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-15 15:48:32 (752) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-15 15:48:35 (1716) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-15 15:48:35 (1717) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-15 15:48:36 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-15 15:48:36 (2518) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LqboIuu0D7/ea_profile.json
* 2024-03-15 15:48:42 (340) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LqboIuu0D7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-15 15:48:42 (301) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-16 02:13:09 (752) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-16 02:13:40 (1716) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-16 02:13:40 (1717) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-16 02:13:41 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-16 02:13:41 (2518) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rq2WvpcRg5/ea_profile.json
* 2024-03-16 02:13:48 (340) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rq2WvpcRg5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-16 02:13:48 (301) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-17 02:13:01 (752) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-17 02:13:04 (1716) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-17 02:13:04 (1717) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-17 02:13:04 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-17 02:13:05 (2518) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GAcPglULdU/ea_profile.json
* 2024-03-17 02:13:11 (340) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GAcPglULdU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-17 02:13:11 (301) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-18 02:12:32 (752) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-18 02:12:35 (1716) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-18 02:12:35 (1717) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-18 02:12:36 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-18 02:12:36 (2518) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZYDE2r1ach/ea_profile.json
* 2024-03-18 02:12:42 (340) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZYDE2r1ach/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-18 02:12:42 (301) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-19 02:12:33 (752) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-19 02:12:36 (1716) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-19 02:12:36 (1717) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-19 02:12:36 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-19 02:12:37 (2518) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Q0nWo4ftSf/ea_profile.json
* 2024-03-19 02:12:43 (340) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Q0nWo4ftSf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-19 02:12:43 (301) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-20 02:12:37 (752) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-20 02:12:40 (1716) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-20 02:12:40 (1717) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-20 02:12:40 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-20 02:12:40 (2518) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aZ9WJvf_Eb/ea_profile.json
* 2024-03-20 02:12:47 (340) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aZ9WJvf_Eb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-20 02:12:47 (301) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-21 02:12:32 (752) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-21 02:12:35 (1716) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-21 02:12:35 (1717) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-21 02:12:36 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-21 02:12:37 (2518) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uLIb7BsMYC/ea_profile.json
* 2024-03-21 02:12:44 (340) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uLIb7BsMYC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-21 02:12:44 (301) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-22 02:12:40 (752) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-22 02:13:11 (1716) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-22 02:13:11 (1717) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-22 02:13:12 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-22 02:13:12 (2518) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WUVli2N1O3/ea_profile.json
* 2024-03-22 02:13:20 (340) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WUVli2N1O3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-22 02:13:20 (301) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-22 15:46:38 (752) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-22 15:47:01 (1716) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-22 15:47:01 (1717) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-22 15:47:01 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-22 15:47:01 (2518) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WSD393QXCp/ea_profile.json
* 2024-03-22 15:47:10 (340) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WSD393QXCp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-22 15:47:10 (301) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-23 02:13:12 (752) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-23 02:13:43 (1716) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-23 02:13:43 (1717) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-23 02:13:43 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-23 02:13:44 (2518) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ea8ljJDeHu/ea_profile.json
* 2024-03-23 02:13:50 (340) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ea8ljJDeHu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-23 02:13:50 (301) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-24 02:13:15 (752) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-24 02:13:47 (1716) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-24 02:13:47 (1717) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-24 02:13:48 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-24 02:13:48 (2518) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4Ajihdz0FZ/ea_profile.json
* 2024-03-24 02:13:54 (340) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4Ajihdz0FZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-24 02:13:54 (301) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-25 02:12:29 (752) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-25 02:12:32 (1716) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-25 02:12:32 (1717) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-25 02:12:32 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-25 02:12:33 (2518) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/soQHR_ax_v/ea_profile.json
* 2024-03-25 02:12:40 (340) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/soQHR_ax_v/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-25 02:12:40 (301) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-26 02:12:34 (752) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-26 02:12:37 (1716) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-26 02:12:37 (1717) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-26 02:12:37 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-26 02:12:37 (2518) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XsFt45etQf/ea_profile.json
* 2024-03-26 02:12:43 (340) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XsFt45etQf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-26 02:12:43 (301) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-27 02:12:35 (752) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-27 02:13:06 (1716) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-27 02:13:06 (1717) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-27 02:13:06 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-27 02:13:08 (2518) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cb2zRMzwCS/ea_profile.json
* 2024-03-27 02:13:15 (340) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cb2zRMzwCS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-27 02:13:15 (301) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-28 02:12:34 (756) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-28 02:13:05 (1754) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-28 02:13:05 (1755) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-28 02:13:06 (997) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-28 02:13:06 (2618) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/D7Nr3UsJkI/ea_profile.json
* 2024-03-28 02:13:13 (344) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/D7Nr3UsJkI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-03-28 02:13:13 (305) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-29 02:12:58 (756) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-29 02:13:29 (1754) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-29 02:13:29 (1755) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-29 02:13:30 (997) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-29 02:13:32 (2618) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ooWmeUsACv/ea_profile.json
* 2024-03-29 02:13:40 (344) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ooWmeUsACv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-03-29 02:13:40 (305) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-29 15:53:57 (344) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID cq6j7t) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> â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(0x2aeb0f8), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2aeb3f8)) called at (eval 6) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2aeb0f8), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 5682
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2b0d7a8)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2b0d7a8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 5692
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2b0d7a8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 1072
	Elevate::Blockers::ElevateScript::_is_up_to_date(Elevate::Blockers::ElevateScript=HASH(0x2a9a3c8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 1047
	Elevate::Blockers::ElevateScript::check(Elevate::Blockers::ElevateScript=HASH(0x2a9a3c8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 389
	Elevate::Blockers::_check_single_blocker(Elevate::Blockers=HASH(0x2a35b80), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 377
	Elevate::Blockers::_check_all_blockers(Elevate::Blockers=HASH(0x2a35b80)) called at /usr/local/cpanel/scripts/elevate-cpanel line 336
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 336
	Elevate::Blockers::_has_blockers(Elevate::Blockers=HASH(0x2a35b80), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 301
	Elevate::Blockers::check(Elevate::Blockers=HASH(0x2a35b80)) called at /usr/local/cpanel/scripts/elevate-cpanel line 6590
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 6532
* 2024-03-29 15:53:57 (305) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-30 02:13:12 (756) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-30 02:13:43 (1754) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-30 02:13:43 (1755) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-30 02:13:44 (997) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-30 02:13:44 (2618) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zhS3PZe9WC/ea_profile.json
* 2024-03-30 02:13:51 (344) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zhS3PZe9WC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-03-30 02:13:51 (305) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-31 02:13:11 (756) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-03-31 02:13:42 (1754) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-03-31 02:13:42 (1755) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-03-31 02:13:43 (997) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-31 02:13:43 (2618) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aMuXmFeQBR/ea_profile.json
* 2024-03-31 02:13:50 (344) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aMuXmFeQBR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-03-31 02:13:50 (305) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-01 02:12:44 (756) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-01 02:13:15 (1754) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-01 02:13:15 (1755) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-01 02:13:16 (997) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-01 02:13:16 (2618) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dfSndbsFvq/ea_profile.json
* 2024-04-01 02:13:22 (344) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dfSndbsFvq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-04-01 02:13:22 (305) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-02 02:12:37 (756) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-02 02:13:08 (1754) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-02 02:13:08 (1755) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-02 02:13:09 (997) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-02 02:13:09 (2618) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PVwX2BtiRT/ea_profile.json
* 2024-04-02 02:13:44 (344) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PVwX2BtiRT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620.
* 2024-04-02 02:13:44 (305) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-03 02:51:36 (759) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-03 02:51:39 (1759) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-03 02:51:39 (1760) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-03 02:51:39 (1001) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-03 02:51:40 (2624) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PX1U9Cfv9e/ea_profile.json
* 2024-04-03 02:51:47 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PX1U9Cfv9e/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-03 02:51:47 (307) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-04 02:12:34 (759) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-04 02:12:38 (1759) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-04 02:12:38 (1760) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-04 02:12:38 (1001) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-04 02:12:39 (2624) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fQ5UoUXb3R/ea_profile.json
* 2024-04-04 02:13:14 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fQ5UoUXb3R/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-04 02:13:14 (307) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-05 02:22:59 (759) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-05 02:23:31 (1759) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-05 02:23:31 (1760) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-05 02:23:31 (1001) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-05 02:23:32 (2624) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ilf0fNi_Ul/ea_profile.json
* 2024-04-05 02:23:39 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ilf0fNi_Ul/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-05 02:23:39 (307) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-05 15:47:10 (759) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-05 15:47:14 (1759) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-05 15:47:14 (1760) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-05 15:47:15 (1001) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-05 15:47:15 (2624) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cqPK3eyyi9/ea_profile.json
* 2024-04-05 15:47:21 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cqPK3eyyi9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-05 15:47:21 (307) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-06 02:13:37 (759) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-06 02:13:49 (1759) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-06 02:13:49 (1760) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-06 02:13:50 (1001) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-06 02:13:51 (2624) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yv6BdR0gwy/ea_profile.json
* 2024-04-06 02:14:02 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yv6BdR0gwy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-06 02:14:02 (307) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-07 02:13:15 (759) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-07 02:13:47 (1759) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-07 02:13:47 (1760) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-07 02:13:47 (1001) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-07 02:13:48 (2624) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pLAV_RM4i1/ea_profile.json
* 2024-04-07 02:13:55 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pLAV_RM4i1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-07 02:13:55 (307) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-08 02:12:37 (759) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-08 02:12:41 (1759) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-08 02:12:41 (1760) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-08 02:12:41 (1001) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-08 02:12:42 (2624) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mC7nNq_1oG/ea_profile.json
* 2024-04-08 02:13:20 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mC7nNq_1oG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-08 02:13:20 (307) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-09 02:12:46 (759) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-09 02:13:17 (1759) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-09 02:13:17 (1760) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-09 02:13:18 (1001) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-09 02:13:18 (2624) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tEZaw4AyV9/ea_profile.json
* 2024-04-09 02:13:25 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tEZaw4AyV9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-09 02:13:25 (307) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-10 02:12:41 (759) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-10 02:13:12 (1759) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-10 02:13:12 (1760) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-10 02:13:13 (1001) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-10 02:13:13 (2624) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aR5Yu_QHAr/ea_profile.json
* 2024-04-10 02:13:20 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aR5Yu_QHAr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-10 02:13:20 (307) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-11 02:12:38 (759) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-11 02:12:41 (1759) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-11 02:12:41 (1760) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-11 02:12:42 (1001) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-11 02:12:42 (2624) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KavP_JWpKw/ea_profile.json
* 2024-04-11 02:12:48 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KavP_JWpKw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-11 02:12:48 (307) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-12 02:12:37 (759) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-12 02:12:40 (1759) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-12 02:12:40 (1760) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-12 02:12:40 (1001) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-12 02:12:41 (2624) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4Lmc98ZlyY/ea_profile.json
* 2024-04-12 02:12:47 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4Lmc98ZlyY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-12 02:12:47 (307) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-12 15:46:35 (759) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-12 15:46:38 (1759) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-12 15:46:38 (1760) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-12 15:46:38 (1001) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-12 15:46:38 (2624) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IUkqrxK_JV/ea_profile.json
* 2024-04-12 15:46:49 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IUkqrxK_JV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-12 15:46:49 (307) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-13 02:13:22 (759) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-13 02:13:25 (1759) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-13 02:13:25 (1760) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-13 02:13:25 (1001) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-13 02:13:25 (2624) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zqz7P6CzJ_/ea_profile.json
* 2024-04-13 02:13:32 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zqz7P6CzJ_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-13 02:13:32 (307) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-14 02:13:16 (759) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-14 02:13:19 (1759) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-14 02:13:19 (1760) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-14 02:13:19 (1001) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-14 02:13:19 (2624) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TGRD6fZD_l/ea_profile.json
* 2024-04-14 02:13:25 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TGRD6fZD_l/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-14 02:13:25 (307) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-15 02:12:30 (759) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-15 02:12:33 (1759) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-15 02:12:33 (1760) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-15 02:12:34 (1001) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-15 02:12:34 (2624) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VYbLyEeoFd/ea_profile.json
* 2024-04-15 02:12:41 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VYbLyEeoFd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-15 02:12:41 (307) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-16 02:12:34 (759) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-16 02:12:37 (1759) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-16 02:12:37 (1760) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-16 02:12:37 (1001) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-16 02:12:38 (2624) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y5ahDcrhct/ea_profile.json
* 2024-04-16 02:12:45 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y5ahDcrhct/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-16 02:12:45 (307) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-17 02:12:34 (776) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-17 02:12:37 (1776) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-17 02:12:37 (1777) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-17 02:12:38 (1018) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-17 02:12:38 (2641) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iZE4EhPFgl/ea_profile.json
* 2024-04-17 02:12:44 (342) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iZE4EhPFgl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-17 02:12:44 (303) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-18 02:12:32 (776) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-18 02:12:35 (1776) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-18 02:12:35 (1777) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-18 02:12:35 (1018) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-18 02:12:35 (2641) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6yUSfEpwsO/ea_profile.json
* 2024-04-18 02:12:40 (342) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6yUSfEpwsO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-18 02:12:40 (303) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-19 02:12:30 (776) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-19 02:12:33 (1776) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-19 02:12:33 (1777) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-19 02:12:33 (1018) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-19 02:12:34 (2641) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YXtR529hVN/ea_profile.json
* 2024-04-19 02:12:42 (342) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YXtR529hVN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-19 02:12:42 (303) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-19 15:47:28 (7106) [[32mINFO[0m] Self-update of script version 34 requested.
* 2024-04-19 15:47:29 (7128) [[32mINFO[0m] Script is up to date.
* 2024-04-19 15:47:30 (192) [[33mWARN[0m] *** 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 194.5.188.42.
Verify whether that IP address is licensed using the following site:

https://verify.cpanel.net/


* 2024-04-19 15:47:32 (776) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-19 15:47:35 (1776) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-19 15:47:35 (1777) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-19 15:47:35 (1018) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-19 15:47:35 (2641) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/V058ahJCVT/ea_profile.json
* 2024-04-19 15:47:40 (342) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/V058ahJCVT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-19 15:47:40 (303) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-20 02:13:03 (7106) [[32mINFO[0m] Self-update of script version 34 requested.
* 2024-04-20 02:13:03 (7128) [[32mINFO[0m] Script is up to date.
* 2024-04-20 02:13:07 (776) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-20 02:13:10 (1776) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-20 02:13:10 (1777) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-20 02:13:10 (1018) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-20 02:13:10 (2641) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KZD3OtUTul/ea_profile.json
* 2024-04-20 02:13:16 (342) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KZD3OtUTul/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-20 02:13:16 (303) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-21 02:18:36 (7106) [[32mINFO[0m] Self-update of script version 34 requested.
* 2024-04-21 02:20:39 (342) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID rvb29g) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: SSL connection failed for raw.githubusercontent.com: SSL wants a read first
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x39b4a10), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3988b38)) called at (eval 6) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x39b4a10), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 5989
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x39b3e28)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x39b3e28)) called at /usr/local/cpanel/scripts/elevate-cpanel line 5999
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x39b3e28)) called at /usr/local/cpanel/scripts/elevate-cpanel line 1093
	Elevate::Blockers::ElevateScript::_is_up_to_date(Elevate::Blockers::ElevateScript=HASH(0x38eacf0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 1068
	Elevate::Blockers::ElevateScript::check(Elevate::Blockers::ElevateScript=HASH(0x38eacf0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 387
	Elevate::Blockers::_check_single_blocker(Elevate::Blockers=HASH(0x352b910), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 375
	Elevate::Blockers::_check_all_blockers(Elevate::Blockers=HASH(0x352b910)) called at /usr/local/cpanel/scripts/elevate-cpanel line 334
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 334
	Elevate::Blockers::_has_blockers(Elevate::Blockers=HASH(0x352b910), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 299
	Elevate::Blockers::check(Elevate::Blockers=HASH(0x352b910)) called at /usr/local/cpanel/scripts/elevate-cpanel line 7019
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 6959
* 2024-04-21 02:20:39 (303) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-22 02:12:31 (7106) [[32mINFO[0m] Self-update of script version 34 requested.
* 2024-04-22 02:12:32 (7128) [[32mINFO[0m] Script is up to date.
* 2024-04-22 02:12:37 (776) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-22 02:12:39 (1776) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-22 02:12:39 (1777) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-22 02:12:40 (1018) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-22 02:12:42 (2641) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eAi2MoWXTx/ea_profile.json
* 2024-04-22 02:12:49 (342) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eAi2MoWXTx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-22 02:12:49 (303) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-23 02:15:06 (7106) [[32mINFO[0m] Self-update of script version 34 requested.
* 2024-04-23 02:17:09 (342) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID sjf3w3) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: SSL connection failed for raw.githubusercontent.com: SSL wants a read first
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x4154420), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x4128508)) called at (eval 6) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x4154420), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 5989
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x4153bc8)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x4153bc8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 5999
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x4153bc8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 1093
	Elevate::Blockers::ElevateScript::_is_up_to_date(Elevate::Blockers::ElevateScript=HASH(0x40dd3f0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 1068
	Elevate::Blockers::ElevateScript::check(Elevate::Blockers::ElevateScript=HASH(0x40dd3f0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 387
	Elevate::Blockers::_check_single_blocker(Elevate::Blockers=HASH(0x40775f8), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 375
	Elevate::Blockers::_check_all_blockers(Elevate::Blockers=HASH(0x40775f8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 334
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 334
	Elevate::Blockers::_has_blockers(Elevate::Blockers=HASH(0x40775f8), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 299
	Elevate::Blockers::check(Elevate::Blockers=HASH(0x40775f8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 7019
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 6959
* 2024-04-23 02:17:09 (303) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-24 02:12:38 (7106) [[32mINFO[0m] Self-update of script version 34 requested.
* 2024-04-24 02:12:39 (7128) [[32mINFO[0m] Script is up to date.
* 2024-04-24 02:12:43 (776) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-24 02:12:45 (1776) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-24 02:12:45 (1777) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-24 02:12:46 (1018) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-24 02:12:46 (2641) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FqctAXNBeL/ea_profile.json
* 2024-04-24 02:12:51 (342) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FqctAXNBeL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-24 02:12:51 (303) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-25 02:12:43 (7106) [[32mINFO[0m] Self-update of script version 34 requested.
* 2024-04-25 02:12:44 (7128) [[32mINFO[0m] Script is up to date.
* 2024-04-25 02:12:47 (776) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-25 02:12:49 (1776) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-25 02:12:49 (1777) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-25 02:12:50 (1018) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-25 02:12:50 (2641) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cLl4BlEuNw/ea_profile.json
* 2024-04-25 02:12:55 (342) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cLl4BlEuNw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2643.
* 2024-04-25 02:12:55 (303) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-26 02:12:49 (7106) [[32mINFO[0m] Self-update of script version 34 requested.
* 2024-04-26 02:12:50 (7111) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-04-26 02:12:51 (7120) [[32mINFO[0m] Script update to version 35 successful.
* 2024-04-26 02:12:56 (779) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-26 02:12:59 (1785) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-26 02:12:59 (1786) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-26 02:13:00 (1029) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-26 02:13:00 (2759) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5R1Eu03kTf/ea_profile.json
* 2024-04-26 02:13:06 (345) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5R1Eu03kTf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2761.
* 2024-04-26 02:13:06 (309) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-26 15:46:42 (7116) [[32mINFO[0m] Self-update of script version 35 requested.
* 2024-04-26 15:46:43 (7138) [[32mINFO[0m] Script is up to date.
* 2024-04-26 15:46:46 (779) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-26 15:46:49 (1785) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-26 15:46:49 (1786) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-26 15:46:49 (1029) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-26 15:46:49 (2759) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vrtcOHo9Uv/ea_profile.json
* 2024-04-26 15:46:55 (345) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vrtcOHo9Uv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2761.
* 2024-04-26 15:46:55 (309) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-27 02:13:31 (7116) [[32mINFO[0m] Self-update of script version 35 requested.
* 2024-04-27 02:13:31 (7138) [[32mINFO[0m] Script is up to date.
* 2024-04-27 02:13:35 (779) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-27 02:13:38 (1785) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-27 02:13:38 (1786) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-27 02:13:38 (1029) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-27 02:13:39 (2759) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SzR9eFfRCg/ea_profile.json
* 2024-04-27 02:13:45 (345) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SzR9eFfRCg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2761.
* 2024-04-27 02:13:45 (309) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-28 02:13:27 (7116) [[32mINFO[0m] Self-update of script version 35 requested.
* 2024-04-28 02:13:28 (7138) [[32mINFO[0m] Script is up to date.
* 2024-04-28 02:13:35 (779) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-28 02:13:52 (1785) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-28 02:13:52 (1786) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-28 02:13:53 (1029) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-28 02:13:54 (2759) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/stZfwXrcyW/ea_profile.json
* 2024-04-28 02:14:00 (345) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/stZfwXrcyW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2761.
* 2024-04-28 02:14:00 (309) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-29 02:16:03 (7116) [[32mINFO[0m] Self-update of script version 35 requested.
* 2024-04-29 02:16:04 (7138) [[32mINFO[0m] Script is up to date.
* 2024-04-29 02:16:05 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2024-04-29 02:16:07 (779) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-29 02:16:10 (1785) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-29 02:16:10 (1786) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-29 02:16:10 (1029) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-29 02:16:11 (2759) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LnsuNV0imK/ea_profile.json
* 2024-04-29 02:16:17 (345) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LnsuNV0imK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2761.
* 2024-04-29 02:16:17 (309) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-30 02:15:43 (7116) [[32mINFO[0m] Self-update of script version 35 requested.
* 2024-04-30 02:15:43 (7138) [[32mINFO[0m] Script is up to date.
* 2024-04-30 02:15:47 (779) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-04-30 02:16:13 (1785) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-04-30 02:16:13 (1786) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-04-30 02:16:13 (1029) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-30 02:16:13 (2759) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/nNysHJUJzk/ea_profile.json
* 2024-04-30 02:17:03 (345) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/nNysHJUJzk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2761.
* 2024-04-30 02:17:03 (309) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-01 02:12:46 (7116) [[32mINFO[0m] Self-update of script version 35 requested.
* 2024-05-01 02:12:47 (7121) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-05-01 02:12:48 (7130) [[32mINFO[0m] Script update to version 36 successful.
* 2024-05-01 02:12:51 (780) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-01 02:13:23 (1786) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-01 02:13:23 (1787) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-01 02:13:23 (1030) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-01 02:13:23 (3150) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/E6J16JcEcR/ea_profile.json
* 2024-05-01 02:13:36 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/E6J16JcEcR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-01 02:13:36 (310) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-02 02:17:59 (7508) [[32mINFO[0m] Self-update of script version 36 requested.
* 2024-05-02 02:20:01 (346) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 5e4hmj) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: SSL connection failed for raw.githubusercontent.com: SSL wants a read first
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2916608), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2916908)) called at (eval 6) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2916608), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 6461
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2918958)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2918958)) called at /usr/local/cpanel/scripts/elevate-cpanel line 6471
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2918958)) called at /usr/local/cpanel/scripts/elevate-cpanel line 1104
	Elevate::Blockers::ElevateScript::_is_up_to_date(Elevate::Blockers::ElevateScript=HASH(0x28b2b10)) called at /usr/local/cpanel/scripts/elevate-cpanel line 1080
	Elevate::Blockers::ElevateScript::check(Elevate::Blockers::ElevateScript=HASH(0x28b2b10)) called at /usr/local/cpanel/scripts/elevate-cpanel line 391
	Elevate::Blockers::_check_single_blocker(Elevate::Blockers=HASH(0x24a6148), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 379
	Elevate::Blockers::_check_all_blockers(Elevate::Blockers=HASH(0x24a6148)) called at /usr/local/cpanel/scripts/elevate-cpanel line 338
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 338
	Elevate::Blockers::_has_blockers(Elevate::Blockers=HASH(0x24a6148), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 306
	Elevate::Blockers::check(Elevate::Blockers=HASH(0x24a6148)) called at /usr/local/cpanel/scripts/elevate-cpanel line 7458
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 7398
* 2024-05-02 02:20:01 (310) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-03 02:12:34 (7508) [[32mINFO[0m] Self-update of script version 36 requested.
* 2024-05-03 02:12:34 (7530) [[32mINFO[0m] Script is up to date.
* 2024-05-03 02:12:37 (780) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-03 02:13:09 (1786) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-03 02:13:09 (1787) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-03 02:13:10 (1030) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-03 02:13:11 (3150) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yeoieQXqt6/ea_profile.json
* 2024-05-03 02:13:18 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yeoieQXqt6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-03 02:13:18 (310) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-03 15:47:52 (7508) [[32mINFO[0m] Self-update of script version 36 requested.
* 2024-05-03 15:47:52 (7530) [[32mINFO[0m] Script is up to date.
* 2024-05-03 15:47:55 (780) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-03 15:48:26 (1786) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-03 15:48:26 (1787) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-03 15:48:27 (1030) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-03 15:48:27 (3150) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/e3yGknXaP_/ea_profile.json
* 2024-05-03 15:48:35 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/e3yGknXaP_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-03 15:48:35 (310) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-04 02:21:09 (7508) [[32mINFO[0m] Self-update of script version 36 requested.
* 2024-05-04 02:21:11 (7530) [[32mINFO[0m] Script is up to date.
* 2024-05-04 02:21:14 (780) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-04 02:21:52 (1786) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-04 02:21:52 (1787) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-04 02:21:53 (1030) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-04 02:21:53 (3150) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0qcZv6x0RI/ea_profile.json
* 2024-05-04 02:22:28 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0qcZv6x0RI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-04 02:22:28 (310) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-05 02:13:02 (7508) [[32mINFO[0m] Self-update of script version 36 requested.
* 2024-05-05 02:13:03 (7530) [[32mINFO[0m] Script is up to date.
* 2024-05-05 02:13:06 (780) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-05 02:13:38 (1786) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-05 02:13:38 (1787) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-05 02:13:38 (1030) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-05 02:13:38 (3150) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Td3okYUEoW/ea_profile.json
* 2024-05-05 02:13:44 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Td3okYUEoW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-05 02:13:44 (310) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-06 02:12:29 (7508) [[32mINFO[0m] Self-update of script version 36 requested.
* 2024-05-06 02:12:30 (7530) [[32mINFO[0m] Script is up to date.
* 2024-05-06 02:12:33 (780) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-06 02:13:04 (1786) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-06 02:13:04 (1787) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-06 02:13:05 (1030) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-06 02:13:05 (3150) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oPWSTTJkpu/ea_profile.json
* 2024-05-06 02:13:42 (346) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oPWSTTJkpu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-06 02:13:42 (310) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-07 02:12:27 (7508) [[32mINFO[0m] Self-update of script version 36 requested.
* 2024-05-07 02:12:28 (7513) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-05-07 02:12:29 (7522) [[32mINFO[0m] Script update to version 37 successful.
* 2024-05-07 02:12:31 (6321) [[32mINFO[0m] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-07 02:12:31 (6322) [[32mINFO[0m] 
* 2024-05-07 02:12:31 (6352) [[32mINFO[0m] 
* 2024-05-07 02:12:33 (783) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-07 02:13:04 (1825) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-07 02:13:04 (1826) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-07 02:13:05 (1033) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-07 02:13:05 (3189) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aVjiDNcvlP/ea_profile.json
* 2024-05-07 02:13:42 (349) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aVjiDNcvlP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-07 02:13:42 (313) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-08 02:12:33 (7548) [[32mINFO[0m] Self-update of script version 37 requested.
* 2024-05-08 02:12:33 (7570) [[32mINFO[0m] Script is up to date.
* 2024-05-08 02:12:35 (6321) [[32mINFO[0m] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-08 02:12:35 (6322) [[32mINFO[0m] 
* 2024-05-08 02:12:35 (6352) [[32mINFO[0m] 
* 2024-05-08 02:12:37 (783) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-08 02:13:08 (1825) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-08 02:13:08 (1826) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-08 02:13:09 (1033) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-08 02:13:09 (3189) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XXkaOZU7Qt/ea_profile.json
* 2024-05-08 02:13:43 (349) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XXkaOZU7Qt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-08 02:13:43 (313) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-09 02:12:24 (7548) [[32mINFO[0m] Self-update of script version 37 requested.
* 2024-05-09 02:12:24 (7570) [[32mINFO[0m] Script is up to date.
* 2024-05-09 02:12:26 (6321) [[32mINFO[0m] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-09 02:12:26 (6322) [[32mINFO[0m] 
* 2024-05-09 02:12:26 (6352) [[32mINFO[0m] 
* 2024-05-09 02:12:28 (783) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-09 02:12:59 (1825) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-09 02:12:59 (1826) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-09 02:13:00 (1033) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-09 02:13:01 (3189) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/wjjBNbj2ky/ea_profile.json
* 2024-05-09 02:13:37 (349) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/wjjBNbj2ky/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-09 02:13:37 (313) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-10 02:12:28 (7548) [[32mINFO[0m] Self-update of script version 37 requested.
* 2024-05-10 02:12:29 (7570) [[32mINFO[0m] Script is up to date.
* 2024-05-10 02:12:30 (6321) [[32mINFO[0m] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-10 02:12:30 (6322) [[32mINFO[0m] 
* 2024-05-10 02:12:30 (6352) [[32mINFO[0m] 
* 2024-05-10 02:12:32 (783) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-10 02:13:03 (1825) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-10 02:13:03 (1826) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-10 02:13:03 (1033) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-10 02:13:04 (3189) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Qu_u_mD479/ea_profile.json
* 2024-05-10 02:13:44 (349) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Qu_u_mD479/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-10 02:13:44 (313) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-10 15:47:07 (7548) [[32mINFO[0m] Self-update of script version 37 requested.
* 2024-05-10 15:47:07 (7570) [[32mINFO[0m] Script is up to date.
* 2024-05-10 15:47:09 (6321) [[32mINFO[0m] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-10 15:47:09 (6322) [[32mINFO[0m] 
* 2024-05-10 15:47:09 (6352) [[32mINFO[0m] 
* 2024-05-10 15:47:10 (783) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-10 15:47:41 (1825) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-10 15:47:41 (1826) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-10 15:47:42 (1033) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-10 15:47:42 (3189) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vi3W0sG7_h/ea_profile.json
* 2024-05-10 15:47:54 (349) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vi3W0sG7_h/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-10 15:47:54 (313) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-11 02:13:19 (7548) [[32mINFO[0m] Self-update of script version 37 requested.
* 2024-05-11 02:13:20 (7570) [[32mINFO[0m] Script is up to date.
* 2024-05-11 02:13:22 (6321) [[32mINFO[0m] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-11 02:13:22 (6322) [[32mINFO[0m] 
* 2024-05-11 02:13:22 (6352) [[32mINFO[0m] 
* 2024-05-11 02:13:23 (783) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-11 02:13:54 (1825) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-11 02:13:54 (1826) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-11 02:13:54 (1033) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-11 02:13:54 (3189) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rN5Ye82tRU/ea_profile.json
* 2024-05-11 02:14:01 (349) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rN5Ye82tRU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-11 02:14:01 (313) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-12 02:13:23 (7548) [[32mINFO[0m] Self-update of script version 37 requested.
* 2024-05-12 02:13:24 (7570) [[32mINFO[0m] Script is up to date.
* 2024-05-12 02:13:26 (6321) [[32mINFO[0m] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-12 02:13:26 (6322) [[32mINFO[0m] 
* 2024-05-12 02:13:26 (6352) [[32mINFO[0m] 
* 2024-05-12 02:13:27 (783) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-12 02:13:58 (1825) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-12 02:13:58 (1826) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-12 02:13:58 (1033) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-12 02:13:58 (3189) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KEBU4b1Cit/ea_profile.json
* 2024-05-12 02:14:09 (349) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KEBU4b1Cit/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-12 02:14:09 (313) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-13 02:12:32 (7548) [[32mINFO[0m] Self-update of script version 37 requested.
* 2024-05-13 02:12:32 (7570) [[32mINFO[0m] Script is up to date.
* 2024-05-13 02:12:34 (6321) [[32mINFO[0m] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-13 02:12:34 (6322) [[32mINFO[0m] 
* 2024-05-13 02:12:34 (6352) [[32mINFO[0m] 
* 2024-05-13 02:12:35 (783) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-13 02:13:06 (1825) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-13 02:13:06 (1826) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-13 02:13:07 (1033) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-13 02:13:07 (3189) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aCaqaJLiLV/ea_profile.json
* 2024-05-13 02:13:43 (349) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aCaqaJLiLV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-13 02:13:43 (313) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-14 02:12:28 (7548) [[32mINFO[0m] Self-update of script version 37 requested.
* 2024-05-14 02:12:28 (7570) [[32mINFO[0m] Script is up to date.
* 2024-05-14 02:12:30 (6321) [[32mINFO[0m] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-14 02:12:30 (6322) [[32mINFO[0m] 
* 2024-05-14 02:12:30 (6352) [[32mINFO[0m] 
* 2024-05-14 02:12:31 (783) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-14 02:13:03 (1825) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-14 02:13:03 (1826) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-14 02:13:04 (1033) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-14 02:13:04 (3189) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xlC21W2EGU/ea_profile.json
* 2024-05-14 02:13:39 (349) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xlC21W2EGU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-14 02:13:39 (313) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-15 02:12:29 (7548) [[32mINFO[0m] Self-update of script version 37 requested.
* 2024-05-15 02:12:34 (7570) [[32mINFO[0m] Script is up to date.
* 2024-05-15 02:12:36 (6321) [[32mINFO[0m] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-15 02:12:36 (6322) [[32mINFO[0m] 
* 2024-05-15 02:12:36 (6352) [[32mINFO[0m] 
* 2024-05-15 02:12:38 (783) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-15 02:13:09 (1825) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-15 02:13:09 (1826) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-15 02:13:10 (1033) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-15 02:13:10 (3189) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/47Jr_AIh9P/ea_profile.json
* 2024-05-15 02:13:44 (349) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/47Jr_AIh9P/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3191.
* 2024-05-15 02:13:44 (313) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-16 02:18:27 (7548) [[32mINFO[0m] Self-update of script version 37 requested.
* 2024-05-16 02:18:27 (7553) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-05-16 02:18:29 (7562) [[32mINFO[0m] Script update to version 38 successful.
* 2024-05-16 02:18:32 (784) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-16 02:26:54 (1039) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-16 02:26:54 (5682) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BGX8NwpLgu/ea_profile.json
* 2024-05-16 02:26:56 (5705) [[32mINFO[0m] Backed up EA4 profile to /tmp/BGX8NwpLgu/ea_profile.json
* 2024-05-16 02:26:57 (201) [[33mWARN[0m] *** Elevation Blocker detected: ***
One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8.
Please remove these packages before continuing the update.
- ea-php54
- ea-php54-build
- ea-php54-libc-client
- ea-php54-libc-client-devel
- ea-php54-libc-client-static
- ea-php54-pear
- ea-php54-php-bcmath
- ea-php54-php-bz2
- ea-php54-php-calendar
- ea-php54-php-cli
- ea-php54-php-common
- ea-php54-php-curl
- ea-php54-php-dba
- ea-php54-php-devel
- ea-php54-php-enchant
- ea-php54-php-exif
- ea-php54-php-fileinfo
- ea-php54-php-fpm
- ea-php54-php-ftp
- ea-php54-php-gd
- ea-php54-php-gettext
- ea-php54-php-gmp
- ea-php54-php-iconv
- ea-php54-php-imap
- ea-php54-php-intl
- ea-php54-php-ioncube10
- ea-php54-php-ldap
- ea-php54-php-litespeed
- ea-php54-php-mbstring
- ea-php54-php-mcrypt
- ea-php54-php-mysqlnd
- ea-php54-php-odbc
- ea-php54-php-pdo
- ea-php54-php-pgsql
- ea-php54-php-posix
- ea-php54-php-process
- ea-php54-php-pspell
- ea-php54-php-snmp
- ea-php54-php-soap
- ea-php54-php-sockets
- ea-php54-php-tidy
- ea-php54-php-xml
- ea-php54-php-xmlrpc
- ea-php54-php-zendguard
- ea-php54-php-zip
- ea-php54-runtime
- ea-php56
- ea-php56-build
- ea-php56-libc-client
- ea-php56-libc-client-devel
- ea-php56-libc-client-static
- ea-php56-pear
- ea-php56-php-bcmath
- ea-php56-php-bz2
- ea-php56-php-calendar
- ea-php56-php-cli
- ea-php56-php-common
- ea-php56-php-curl
- ea-php56-php-dba
- ea-php56-php-devel
- ea-php56-php-enchant
- ea-php56-php-exif
- ea-php56-php-fileinfo
- ea-php56-php-fpm
- ea-php56-php-ftp
- ea-php56-php-gd
- ea-php56-php-gettext
- ea-php56-php-gmp
- ea-php56-php-iconv
- ea-php56-php-imap
- ea-php56-php-intl
- ea-php56-php-ioncube10
- ea-php56-php-ldap
- ea-php56-php-litespeed
- ea-php56-php-mbstring
- ea-php56-php-mcrypt
- ea-php56-php-mysqlnd
- ea-php56-php-odbc
- ea-php56-php-opcache
- ea-php56-php-pdo
- ea-php56-php-pgsql
- ea-php56-php-posix
- ea-php56-php-process
- ea-php56-php-pspell
- ea-php56-php-snmp
- ea-php56-php-soap
- ea-php56-php-sockets
- ea-php56-php-sourceguardian
- ea-php56-php-tidy
- ea-php56-php-xml
- ea-php56-php-xmlrpc
- ea-php56-php-zip
- ea-php56-runtime

* 2024-05-16 02:26:59 (201) [[33mWARN[0m] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.90.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.102.1.el7.x86_64). This could be due to the kernel
being changed by an update, meaning that a reboot should resolve this.
However, this also could indicate that the system does not have control
over which kernel and early boot environment (initrd) is used upon
reboot, which is required to upgrade the operating system with this
script.

If this message remains after a reboot, your server may have been
configured to boot into a particular kernel directly rather than to an
instance of the GRUB2 boot loader. This often happens to virtualized
servers, but physical servers also can have this problem under certain
configurations. Your provider may have a solution to allow booting into
GRUB2; contact them for further information.

* 2024-05-16 02:27:07 (314) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-17 02:12:45 (7726) [[32mINFO[0m] Self-update of script version 38 requested.
* 2024-05-17 02:12:46 (7748) [[32mINFO[0m] Script is up to date.
* 2024-05-17 02:12:50 (784) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-17 02:13:21 (1932) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-17 02:13:21 (1933) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-17 02:13:22 (1039) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-17 02:13:23 (5682) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hz46LjZy91/ea_profile.json
* 2024-05-17 02:13:58 (350) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hz46LjZy91/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-17 02:13:58 (314) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-17 15:46:58 (7726) [[32mINFO[0m] Self-update of script version 38 requested.
* 2024-05-17 15:46:59 (7748) [[32mINFO[0m] Script is up to date.
* 2024-05-17 15:47:02 (784) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-17 15:47:33 (1932) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-17 15:47:33 (1933) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-17 15:47:34 (1039) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-17 15:47:34 (5682) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QMD1YBmAsz/ea_profile.json
* 2024-05-17 15:47:41 (350) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QMD1YBmAsz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-17 15:47:41 (314) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-18 02:13:04 (7726) [[32mINFO[0m] Self-update of script version 38 requested.
* 2024-05-18 02:13:05 (7748) [[32mINFO[0m] Script is up to date.
* 2024-05-18 02:13:09 (784) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-18 02:13:40 (1932) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-18 02:13:40 (1933) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-18 02:13:41 (1039) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-18 02:13:42 (5682) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CQJeU_5Fav/ea_profile.json
* 2024-05-18 02:13:47 (350) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CQJeU_5Fav/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-18 02:13:47 (314) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-19 02:13:00 (7726) [[32mINFO[0m] Self-update of script version 38 requested.
* 2024-05-19 02:13:01 (7748) [[32mINFO[0m] Script is up to date.
* 2024-05-19 02:13:04 (784) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-19 02:13:35 (1932) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-19 02:13:35 (1933) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-19 02:13:36 (1039) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-19 02:13:36 (5682) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/t5J21yBCXq/ea_profile.json
* 2024-05-19 02:13:43 (350) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/t5J21yBCXq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-19 02:13:43 (314) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-20 02:12:30 (7726) [[32mINFO[0m] Self-update of script version 38 requested.
* 2024-05-20 02:12:30 (7748) [[32mINFO[0m] Script is up to date.
* 2024-05-20 02:12:34 (784) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-20 02:13:05 (1932) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-20 02:13:05 (1933) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-20 02:13:05 (1039) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-20 02:13:05 (5682) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y3JkztxH_f/ea_profile.json
* 2024-05-20 02:13:40 (350) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y3JkztxH_f/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-20 02:13:40 (314) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-21 02:12:30 (7726) [[32mINFO[0m] Self-update of script version 38 requested.
* 2024-05-21 02:12:31 (7748) [[32mINFO[0m] Script is up to date.
* 2024-05-21 02:12:34 (784) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-21 02:13:05 (1932) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-21 02:13:05 (1933) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-21 02:13:06 (1039) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-21 02:13:06 (5682) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/phDchWEJPi/ea_profile.json
* 2024-05-21 02:13:41 (350) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/phDchWEJPi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-21 02:13:41 (314) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-22 02:13:18 (7726) [[32mINFO[0m] Self-update of script version 38 requested.
* 2024-05-22 02:13:18 (7748) [[32mINFO[0m] Script is up to date.
* 2024-05-22 02:13:22 (784) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-22 02:13:53 (1932) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-22 02:13:53 (1933) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-22 02:13:54 (1039) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-22 02:13:54 (5682) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RI39SSTsGq/ea_profile.json
* 2024-05-22 02:14:00 (350) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RI39SSTsGq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-22 02:14:00 (314) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-23 02:12:24 (7726) [[32mINFO[0m] Self-update of script version 38 requested.
* 2024-05-23 02:12:25 (7748) [[32mINFO[0m] Script is up to date.
* 2024-05-23 02:12:28 (784) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-23 02:13:00 (1932) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-23 02:13:00 (1933) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-23 02:13:01 (1039) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-23 02:13:01 (5682) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jmGZUhy6k6/ea_profile.json
* 2024-05-23 02:13:36 (350) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jmGZUhy6k6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-23 02:13:36 (314) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-24 02:12:29 (7726) [[32mINFO[0m] Self-update of script version 38 requested.
* 2024-05-24 02:12:30 (7748) [[32mINFO[0m] Script is up to date.
* 2024-05-24 02:12:35 (784) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-24 02:13:06 (1932) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-24 02:13:06 (1933) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-24 02:13:06 (1039) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-24 02:13:06 (5682) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6Yp0zSpZsd/ea_profile.json
* 2024-05-24 02:13:43 (350) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6Yp0zSpZsd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-24 02:13:43 (314) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-24 15:47:03 (7726) [[32mINFO[0m] Self-update of script version 38 requested.
* 2024-05-24 15:47:04 (7748) [[32mINFO[0m] Script is up to date.
* 2024-05-24 15:47:07 (784) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-24 15:47:38 (1932) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-24 15:47:38 (1933) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-24 15:47:39 (1039) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-24 15:47:39 (5682) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Iis89Tkh9U/ea_profile.json
* 2024-05-24 15:47:47 (350) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Iis89Tkh9U/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-24 15:47:47 (314) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-25 02:13:08 (7726) [[32mINFO[0m] Self-update of script version 38 requested.
* 2024-05-25 02:13:09 (7748) [[32mINFO[0m] Script is up to date.
* 2024-05-25 02:13:12 (784) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-25 02:13:43 (1932) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-25 02:13:43 (1933) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-25 02:13:44 (1039) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-25 02:13:44 (5682) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AoFtXt7NHu/ea_profile.json
* 2024-05-25 02:13:50 (350) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AoFtXt7NHu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-25 02:13:50 (314) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-26 02:12:57 (7726) [[32mINFO[0m] Self-update of script version 38 requested.
* 2024-05-26 02:12:58 (7748) [[32mINFO[0m] Script is up to date.
* 2024-05-26 02:13:01 (784) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-26 02:13:32 (1932) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-26 02:13:32 (1933) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-26 02:13:33 (1039) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-26 02:13:33 (5682) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YERdqBJmEG/ea_profile.json
* 2024-05-26 02:13:39 (350) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YERdqBJmEG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-26 02:13:39 (314) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-27 02:12:25 (7726) [[32mINFO[0m] Self-update of script version 38 requested.
* 2024-05-27 02:12:25 (7748) [[32mINFO[0m] Script is up to date.
* 2024-05-27 02:12:28 (784) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-27 02:13:00 (1932) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-27 02:13:00 (1933) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-27 02:13:00 (1039) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-27 02:13:01 (5682) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/n5oGhULRv2/ea_profile.json
* 2024-05-27 02:13:35 (350) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/n5oGhULRv2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-27 02:13:35 (314) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-28 02:21:54 (7726) [[32mINFO[0m] Self-update of script version 38 requested.
* 2024-05-28 02:21:59 (7748) [[32mINFO[0m] Script is up to date.
* 2024-05-28 02:22:03 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2024-05-28 02:22:04 (784) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-28 02:22:52 (1932) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-28 02:22:52 (1933) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-28 02:22:53 (1039) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-28 02:22:53 (5682) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mZTbQfrbEe/ea_profile.json
* 2024-05-28 02:23:45 (350) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mZTbQfrbEe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-28 02:23:45 (314) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-29 02:12:31 (7726) [[32mINFO[0m] Self-update of script version 38 requested.
* 2024-05-29 02:12:32 (7748) [[32mINFO[0m] Script is up to date.
* 2024-05-29 02:12:36 (784) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-29 02:13:07 (1932) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-29 02:13:07 (1933) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-29 02:13:08 (1039) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-29 02:13:08 (5682) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0K9gOoVLgL/ea_profile.json
* 2024-05-29 02:13:44 (350) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0K9gOoVLgL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5684.
* 2024-05-29 02:13:44 (314) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-30 02:12:56 (7726) [[32mINFO[0m] Self-update of script version 38 requested.
* 2024-05-30 02:12:56 (7731) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-05-30 02:12:58 (7740) [[32mINFO[0m] Script update to version 39 successful.
* 2024-05-30 02:13:03 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-30 02:13:05 (1981) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-30 02:13:05 (1982) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-30 02:13:06 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-30 02:13:06 (5750) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UZnTtqdsPr/ea_profile.json
* 2024-05-30 02:13:12 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UZnTtqdsPr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-05-30 02:13:12 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-31 02:12:25 (7795) [[32mINFO[0m] Self-update of script version 39 requested.
* 2024-05-31 02:12:25 (7817) [[32mINFO[0m] Script is up to date.
* 2024-05-31 02:12:30 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-31 02:13:01 (1981) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-31 02:13:01 (1982) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-31 02:13:01 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-31 02:13:02 (5750) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y0HQ_PULz6/ea_profile.json
* 2024-05-31 02:13:37 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y0HQ_PULz6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-05-31 02:13:37 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-31 15:47:37 (7795) [[32mINFO[0m] Self-update of script version 39 requested.
* 2024-05-31 15:47:38 (7817) [[32mINFO[0m] Script is up to date.
* 2024-05-31 15:47:41 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-05-31 15:47:49 (1981) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-05-31 15:47:49 (1982) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-05-31 15:47:49 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-31 15:47:49 (5750) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NmVLx8HRSW/ea_profile.json
* 2024-05-31 15:47:58 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NmVLx8HRSW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-05-31 15:47:58 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-01 02:13:06 (7795) [[32mINFO[0m] Self-update of script version 39 requested.
* 2024-06-01 02:13:07 (7817) [[32mINFO[0m] Script is up to date.
* 2024-06-01 02:13:10 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-01 02:13:14 (1981) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-01 02:13:14 (1982) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-01 02:13:14 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-01 02:13:15 (5750) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GuA6yaN7sc/ea_profile.json
* 2024-06-01 02:13:49 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GuA6yaN7sc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-06-01 02:13:49 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-02 02:21:57 (7795) [[32mINFO[0m] Self-update of script version 39 requested.
* 2024-06-02 02:21:57 (7817) [[32mINFO[0m] Script is up to date.
* 2024-06-02 02:22:00 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: Failed to download signature at URL 'http://repo-ir.amazeservice.net/cpanelsync/TIERS.json.asc'.
* 2024-06-02 02:22:00 (353) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 2339.
* 2024-06-02 02:22:00 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-03 02:12:32 (7795) [[32mINFO[0m] Self-update of script version 39 requested.
* 2024-06-03 02:12:33 (7817) [[32mINFO[0m] Script is up to date.
* 2024-06-03 02:12:36 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-03 02:13:07 (1981) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-03 02:13:07 (1982) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-03 02:13:08 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-03 02:13:08 (5750) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cFN9dXD1vp/ea_profile.json
* 2024-06-03 02:13:14 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cFN9dXD1vp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-06-03 02:13:14 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-04 02:12:27 (7795) [[32mINFO[0m] Self-update of script version 39 requested.
* 2024-06-04 02:12:28 (7817) [[32mINFO[0m] Script is up to date.
* 2024-06-04 02:12:30 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-04 02:13:02 (1981) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-04 02:13:02 (1982) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-04 02:13:02 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-04 02:13:02 (5750) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yhLF38CtD5/ea_profile.json
* 2024-06-04 02:13:37 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yhLF38CtD5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-06-04 02:13:37 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-05 02:12:29 (7795) [[32mINFO[0m] Self-update of script version 39 requested.
* 2024-06-05 02:12:29 (7817) [[32mINFO[0m] Script is up to date.
* 2024-06-05 02:12:33 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-05 02:13:04 (1981) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-05 02:13:04 (1982) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-05 02:13:05 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-05 02:13:05 (5750) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/obUfIMKA_n/ea_profile.json
* 2024-06-05 02:13:41 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/obUfIMKA_n/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5752.
* 2024-06-05 02:13:41 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-06 02:12:07 (7795) [[32mINFO[0m] Self-update of script version 39 requested.
* 2024-06-06 02:12:08 (7800) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-06-06 02:12:09 (7809) [[32mINFO[0m] Script update to version 40 successful.
* 2024-06-06 02:12:11 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-06 02:12:14 (1982) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-06 02:12:14 (1983) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-06 02:12:14 (6579) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-06 02:12:14 (6580) [[32mINFO[0m] 
* 2024-06-06 02:12:14 (6593) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-06 02:12:14 (6593) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-06 02:12:14 (6593) [[32mINFO[0m]               : epel extras updates
* 2024-06-06 02:12:14 (6593) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-06 02:12:14 (6593) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-06 02:12:14 (6610) [[32mINFO[0m] 
* 2024-06-06 02:12:18 (1992) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-06 02:12:18 (1993) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-06 02:12:18 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-06 02:12:18 (5762) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fwkzq9Cs9V/ea_profile.json
* 2024-06-06 02:12:25 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fwkzq9Cs9V/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-06 02:12:25 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-07 02:12:13 (7807) [[32mINFO[0m] Self-update of script version 40 requested.
* 2024-06-07 02:12:14 (7829) [[32mINFO[0m] Script is up to date.
* 2024-06-07 02:12:16 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-07 02:12:19 (1982) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-07 02:12:19 (1983) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-07 02:12:19 (6579) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-07 02:12:19 (6580) [[32mINFO[0m] 
* 2024-06-07 02:12:19 (6593) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-07 02:12:19 (6593) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-07 02:12:19 (6593) [[32mINFO[0m]               : epel extras updates
* 2024-06-07 02:12:19 (6593) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-07 02:12:19 (6593) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-07 02:12:19 (6610) [[32mINFO[0m] 
* 2024-06-07 02:12:22 (1992) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-07 02:12:22 (1993) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-07 02:12:22 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-07 02:12:22 (5762) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/W4TccyfGUO/ea_profile.json
* 2024-06-07 02:12:27 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/W4TccyfGUO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-07 02:12:27 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-07 15:46:49 (7807) [[32mINFO[0m] Self-update of script version 40 requested.
* 2024-06-07 15:46:49 (7829) [[32mINFO[0m] Script is up to date.
* 2024-06-07 15:46:51 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-07 15:47:25 (1982) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://httpupdate.cpanel.net/cpanel-plugins-c7-x86_64-mirrorlist error was
12: Timeout on http://httpupdate.cpanel.net/cpanel-plugins-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-07 15:47:25 (1983) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-07 15:47:25 (6579) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-07 15:47:25 (6580) [[32mINFO[0m] 
* 2024-06-07 15:47:25 (6593) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-07 15:47:25 (6593) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-07 15:47:25 (6593) [[32mINFO[0m]               : epel extras updates
* 2024-06-07 15:47:25 (6593) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-07 15:47:25 (6593) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-07 15:47:25 (6610) [[32mINFO[0m] 
* 2024-06-07 15:47:55 (1992) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-07 15:47:55 (1993) [[31mERROR[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2024-06-07 15:47:56 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-07 15:47:56 (5762) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kQWSIBc8py/ea_profile.json
* 2024-06-07 15:48:27 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kQWSIBc8py/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-07 15:48:27 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-08 02:12:32 (7807) [[32mINFO[0m] Self-update of script version 40 requested.
* 2024-06-08 02:12:33 (7829) [[32mINFO[0m] Script is up to date.
* 2024-06-08 02:12:35 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-08 02:12:39 (1982) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-08 02:12:39 (1983) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-08 02:12:39 (6579) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-08 02:12:39 (6580) [[32mINFO[0m] 
* 2024-06-08 02:12:39 (6593) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-08 02:12:39 (6593) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-08 02:12:39 (6593) [[32mINFO[0m]               : epel extras updates
* 2024-06-08 02:12:39 (6593) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-08 02:12:39 (6593) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-08 02:12:39 (6610) [[32mINFO[0m] 
* 2024-06-08 02:12:44 (1992) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-08 02:12:44 (1993) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-08 02:12:44 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-08 02:12:44 (5762) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ccg9Yqn8n4/ea_profile.json
* 2024-06-08 02:13:19 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ccg9Yqn8n4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-08 02:13:19 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-09 02:12:32 (7807) [[32mINFO[0m] Self-update of script version 40 requested.
* 2024-06-09 02:12:32 (7829) [[32mINFO[0m] Script is up to date.
* 2024-06-09 02:12:34 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-09 02:12:37 (1982) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-09 02:12:37 (1983) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-09 02:12:37 (6579) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-09 02:12:37 (6580) [[32mINFO[0m] 
* 2024-06-09 02:12:37 (6593) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-09 02:12:37 (6593) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-09 02:12:37 (6593) [[32mINFO[0m]               : epel extras updates
* 2024-06-09 02:12:37 (6593) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-09 02:12:37 (6593) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-09 02:12:37 (6610) [[32mINFO[0m] 
* 2024-06-09 02:12:41 (1992) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-09 02:12:41 (1993) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-09 02:12:41 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-09 02:12:41 (5762) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/i4htVQY3lL/ea_profile.json
* 2024-06-09 02:12:47 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/i4htVQY3lL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-09 02:12:47 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-10 02:12:13 (7807) [[32mINFO[0m] Self-update of script version 40 requested.
* 2024-06-10 02:12:14 (7829) [[32mINFO[0m] Script is up to date.
* 2024-06-10 02:12:16 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-10 02:12:19 (1982) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-10 02:12:19 (1983) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-10 02:12:19 (6579) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-10 02:12:19 (6580) [[32mINFO[0m] 
* 2024-06-10 02:12:19 (6593) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-10 02:12:19 (6593) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-10 02:12:19 (6593) [[32mINFO[0m]               : epel extras updates
* 2024-06-10 02:12:19 (6593) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-10 02:12:19 (6593) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-10 02:12:19 (6610) [[32mINFO[0m] 
* 2024-06-10 02:12:23 (1992) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-10 02:12:23 (1993) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-10 02:12:23 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-10 02:12:23 (5762) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y8OQ6INGWx/ea_profile.json
* 2024-06-10 02:12:29 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y8OQ6INGWx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-10 02:12:29 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-11 02:12:13 (7807) [[32mINFO[0m] Self-update of script version 40 requested.
* 2024-06-11 02:12:14 (7829) [[32mINFO[0m] Script is up to date.
* 2024-06-11 02:12:16 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-11 02:12:21 (1982) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-11 02:12:21 (1983) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-11 02:12:21 (6579) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-11 02:12:21 (6580) [[32mINFO[0m] 
* 2024-06-11 02:12:21 (6593) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-11 02:12:21 (6593) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-11 02:12:21 (6593) [[32mINFO[0m]               : epel extras updates
* 2024-06-11 02:12:21 (6593) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-11 02:12:21 (6593) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-11 02:12:21 (6610) [[32mINFO[0m] 
* 2024-06-11 02:12:25 (1992) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-11 02:12:25 (1993) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-11 02:12:25 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-11 02:12:25 (5762) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HZKqDMjYHe/ea_profile.json
* 2024-06-11 02:12:31 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HZKqDMjYHe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-11 02:12:31 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-12 02:12:18 (7807) [[32mINFO[0m] Self-update of script version 40 requested.
* 2024-06-12 02:12:18 (7829) [[32mINFO[0m] Script is up to date.
* 2024-06-12 02:12:20 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-12 02:12:23 (1982) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-12 02:12:23 (1983) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-12 02:12:23 (6579) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-12 02:12:23 (6580) [[32mINFO[0m] 
* 2024-06-12 02:12:24 (6593) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-12 02:12:24 (6593) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-12 02:12:24 (6593) [[32mINFO[0m]               : epel extras updates
* 2024-06-12 02:12:24 (6593) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-12 02:12:24 (6593) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-12 02:12:24 (6610) [[32mINFO[0m] 
* 2024-06-12 02:12:28 (1992) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-12 02:12:28 (1993) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-12 02:12:28 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-12 02:12:28 (5762) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/D3ZGxJbXLA/ea_profile.json
* 2024-06-12 02:12:35 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/D3ZGxJbXLA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5764.
* 2024-06-12 02:12:35 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-13 02:12:17 (7807) [[32mINFO[0m] Self-update of script version 40 requested.
* 2024-06-13 02:12:17 (7812) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-06-13 02:12:19 (7821) [[32mINFO[0m] Script update to version 41 successful.
* 2024-06-13 02:12:21 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-13 02:12:24 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-13 02:12:24 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-13 02:12:24 (6590) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-13 02:12:24 (6591) [[32mINFO[0m] 
* 2024-06-13 02:12:24 (6604) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-13 02:12:24 (6604) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-13 02:12:24 (6604) [[32mINFO[0m]               : epel extras updates
* 2024-06-13 02:12:24 (6604) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-13 02:12:24 (6604) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-13 02:12:24 (6621) [[32mINFO[0m] 
* 2024-06-13 02:12:27 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-13 02:12:27 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-13 02:12:28 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-13 02:12:28 (5773) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9p9vzrTgYW/ea_profile.json
* 2024-06-13 02:12:33 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9p9vzrTgYW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-13 02:12:33 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-14 02:12:55 (7818) [[32mINFO[0m] Self-update of script version 41 requested.
* 2024-06-14 02:12:56 (7840) [[32mINFO[0m] Script is up to date.
* 2024-06-14 02:12:58 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-14 02:13:29 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-14 02:13:29 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-14 02:13:29 (6590) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-14 02:13:29 (6591) [[32mINFO[0m] 
* 2024-06-14 02:13:29 (6604) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-14 02:13:29 (6604) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-14 02:13:29 (6604) [[32mINFO[0m]               : epel extras updates
* 2024-06-14 02:13:29 (6604) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-14 02:13:29 (6604) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-14 02:13:29 (6621) [[32mINFO[0m] 
* 2024-06-14 02:13:36 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-14 02:13:36 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-14 02:13:36 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-14 02:13:36 (5773) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TcRcZgn7Oy/ea_profile.json
* 2024-06-14 02:13:42 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TcRcZgn7Oy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-14 02:13:42 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-14 15:46:19 (7818) [[32mINFO[0m] Self-update of script version 41 requested.
* 2024-06-14 15:46:19 (7840) [[32mINFO[0m] Script is up to date.
* 2024-06-14 15:46:22 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-14 15:46:25 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-14 15:46:25 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-14 15:46:25 (6590) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-14 15:46:25 (6591) [[32mINFO[0m] 
* 2024-06-14 15:46:25 (6604) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-14 15:46:25 (6604) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-14 15:46:25 (6604) [[32mINFO[0m]               : epel extras updates
* 2024-06-14 15:46:25 (6604) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-14 15:46:25 (6604) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-14 15:46:25 (6621) [[32mINFO[0m] 
* 2024-06-14 15:46:29 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-14 15:46:29 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-14 15:46:30 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-14 15:46:30 (5773) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5KA2Pc_rEP/ea_profile.json
* 2024-06-14 15:46:35 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5KA2Pc_rEP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-14 15:46:35 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-15 02:12:43 (7818) [[32mINFO[0m] Self-update of script version 41 requested.
* 2024-06-15 02:12:43 (7840) [[32mINFO[0m] Script is up to date.
* 2024-06-15 02:12:46 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-15 02:12:50 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-15 02:12:50 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-15 02:12:50 (6590) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-15 02:12:50 (6591) [[32mINFO[0m] 
* 2024-06-15 02:12:50 (6604) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-15 02:12:50 (6604) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-15 02:12:50 (6604) [[32mINFO[0m]               : epel extras updates
* 2024-06-15 02:12:50 (6604) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-15 02:12:50 (6604) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-15 02:12:50 (6621) [[32mINFO[0m] 
* 2024-06-15 02:13:22 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-15 02:13:22 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-15 02:13:22 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-15 02:13:22 (5773) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/y4CJfpS6VB/ea_profile.json
* 2024-06-15 02:13:29 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/y4CJfpS6VB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-15 02:13:29 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-16 02:12:41 (7818) [[32mINFO[0m] Self-update of script version 41 requested.
* 2024-06-16 02:12:41 (7840) [[32mINFO[0m] Script is up to date.
* 2024-06-16 02:12:44 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-16 02:12:46 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-16 02:12:46 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-16 02:12:46 (6590) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-16 02:12:46 (6591) [[32mINFO[0m] 
* 2024-06-16 02:12:46 (6604) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-16 02:12:47 (6604) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-16 02:12:47 (6604) [[32mINFO[0m]               : epel extras updates
* 2024-06-16 02:12:47 (6604) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-16 02:12:47 (6604) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-16 02:12:47 (6621) [[32mINFO[0m] 
* 2024-06-16 02:12:50 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-16 02:12:50 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-16 02:12:50 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-16 02:12:50 (5773) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mGtae7bRp_/ea_profile.json
* 2024-06-16 02:12:56 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mGtae7bRp_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-16 02:12:56 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-17 02:12:11 (7818) [[32mINFO[0m] Self-update of script version 41 requested.
* 2024-06-17 02:12:12 (7840) [[32mINFO[0m] Script is up to date.
* 2024-06-17 02:12:14 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-17 02:12:17 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-17 02:12:17 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-17 02:12:17 (6590) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-17 02:12:17 (6591) [[32mINFO[0m] 
* 2024-06-17 02:12:17 (6604) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-17 02:12:17 (6604) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-17 02:12:17 (6604) [[32mINFO[0m]               : epel extras updates
* 2024-06-17 02:12:17 (6604) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-17 02:12:17 (6604) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-17 02:12:17 (6621) [[32mINFO[0m] 
* 2024-06-17 02:12:22 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-17 02:12:22 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-17 02:12:22 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-17 02:12:22 (5773) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Sc_UOBnMuo/ea_profile.json
* 2024-06-17 02:12:28 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Sc_UOBnMuo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-17 02:12:28 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-18 02:12:18 (7818) [[32mINFO[0m] Self-update of script version 41 requested.
* 2024-06-18 02:12:19 (7840) [[32mINFO[0m] Script is up to date.
* 2024-06-18 02:12:21 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-18 02:12:24 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-18 02:12:24 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-18 02:12:24 (6590) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-18 02:12:24 (6591) [[32mINFO[0m] 
* 2024-06-18 02:12:24 (6604) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-18 02:12:24 (6604) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-18 02:12:24 (6604) [[32mINFO[0m]               : epel extras updates
* 2024-06-18 02:12:24 (6604) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-18 02:12:24 (6604) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-18 02:12:24 (6621) [[32mINFO[0m] 
* 2024-06-18 02:12:27 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-18 02:12:27 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-18 02:12:27 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-18 02:12:27 (5773) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rZKxqfQmf0/ea_profile.json
* 2024-06-18 02:12:32 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rZKxqfQmf0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-18 02:12:32 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-19 02:15:16 (7818) [[32mINFO[0m] Self-update of script version 41 requested.
* 2024-06-19 02:15:16 (7840) [[32mINFO[0m] Script is up to date.
* 2024-06-19 02:15:19 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-19 02:15:21 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-19 02:15:21 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-19 02:15:21 (6590) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-19 02:15:21 (6591) [[32mINFO[0m] 
* 2024-06-19 02:15:22 (6604) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-19 02:15:22 (6604) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-19 02:15:22 (6604) [[32mINFO[0m]               : epel extras updates
* 2024-06-19 02:15:22 (6604) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-19 02:15:22 (6604) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-19 02:15:22 (6621) [[32mINFO[0m] 
* 2024-06-19 02:15:25 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-19 02:15:25 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-19 02:15:25 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-19 02:15:25 (5773) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kfKBd0r3ph/ea_profile.json
* 2024-06-19 02:15:30 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kfKBd0r3ph/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-19 02:15:30 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-20 02:12:13 (7818) [[32mINFO[0m] Self-update of script version 41 requested.
* 2024-06-20 02:12:14 (7840) [[32mINFO[0m] Script is up to date.
* 2024-06-20 02:12:16 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-20 02:12:19 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-20 02:12:19 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-20 02:12:19 (6590) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-20 02:12:19 (6591) [[32mINFO[0m] 
* 2024-06-20 02:12:19 (6604) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-20 02:12:19 (6604) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-20 02:12:19 (6604) [[32mINFO[0m]               : epel extras updates
* 2024-06-20 02:12:19 (6604) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-20 02:12:19 (6604) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-20 02:12:19 (6621) [[32mINFO[0m] 
* 2024-06-20 02:12:22 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-20 02:12:22 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-20 02:12:23 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-20 02:12:23 (5773) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/X9Qi7eCb7m/ea_profile.json
* 2024-06-20 02:12:28 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/X9Qi7eCb7m/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-20 02:12:28 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-20 09:54:54 (7818) [[32mINFO[0m] Self-update of script version 41 requested.
* 2024-06-20 09:54:55 (7840) [[32mINFO[0m] Script is up to date.
* 2024-06-20 09:54:57 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-20 09:55:00 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-20 09:55:00 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-20 09:55:00 (6590) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-20 09:55:00 (6591) [[32mINFO[0m] 
* 2024-06-20 09:55:00 (6604) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-20 09:55:00 (6604) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-20 09:55:00 (6604) [[32mINFO[0m]               : epel extras updates
* 2024-06-20 09:55:00 (6604) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-20 09:55:00 (6604) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-20 09:55:00 (6621) [[32mINFO[0m] 
* 2024-06-20 09:55:04 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-20 09:55:04 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-20 09:55:05 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-20 09:55:05 (5773) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iV9278hBOi/ea_profile.json
* 2024-06-20 09:55:10 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iV9278hBOi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-20 09:55:10 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-21 02:12:08 (7818) [[32mINFO[0m] Self-update of script version 41 requested.
* 2024-06-21 02:12:08 (7840) [[32mINFO[0m] Script is up to date.
* 2024-06-21 02:12:11 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-21 02:12:13 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-21 02:12:13 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-21 02:12:13 (6590) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-21 02:12:13 (6591) [[32mINFO[0m] 
* 2024-06-21 02:12:13 (6604) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-21 02:12:13 (6604) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-21 02:12:13 (6604) [[32mINFO[0m]               : epel extras updates
* 2024-06-21 02:12:13 (6604) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-21 02:12:13 (6604) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-21 02:12:13 (6621) [[32mINFO[0m] 
* 2024-06-21 02:12:17 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-21 02:12:17 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-21 02:12:17 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-21 02:12:17 (5773) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SfxCHa5wzx/ea_profile.json
* 2024-06-21 02:12:22 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SfxCHa5wzx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-21 02:12:22 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-21 15:46:18 (7818) [[32mINFO[0m] Self-update of script version 41 requested.
* 2024-06-21 15:46:18 (7840) [[32mINFO[0m] Script is up to date.
* 2024-06-21 15:46:21 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-21 15:46:24 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-21 15:46:24 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-21 15:46:24 (6590) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-21 15:46:24 (6591) [[32mINFO[0m] 
* 2024-06-21 15:46:24 (6604) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-21 15:46:24 (6604) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-21 15:46:24 (6604) [[32mINFO[0m]               : epel extras updates
* 2024-06-21 15:46:24 (6604) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-21 15:46:24 (6604) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-21 15:46:24 (6621) [[32mINFO[0m] 
* 2024-06-21 15:46:28 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-21 15:46:28 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-21 15:46:28 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-21 15:46:28 (5773) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UjsbOLXJM0/ea_profile.json
* 2024-06-21 15:46:42 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UjsbOLXJM0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-21 15:46:42 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-22 02:12:38 (7818) [[32mINFO[0m] Self-update of script version 41 requested.
* 2024-06-22 02:12:39 (7840) [[32mINFO[0m] Script is up to date.
* 2024-06-22 02:12:41 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-22 02:12:44 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-22 02:12:44 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-22 02:12:44 (6590) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-22 02:12:44 (6591) [[32mINFO[0m] 
* 2024-06-22 02:12:44 (6604) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-22 02:12:44 (6604) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-22 02:12:44 (6604) [[32mINFO[0m]               : epel extras updates
* 2024-06-22 02:12:44 (6604) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-22 02:12:44 (6604) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-22 02:12:44 (6621) [[32mINFO[0m] 
* 2024-06-22 02:12:48 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-22 02:12:48 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-22 02:12:49 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-22 02:12:49 (5773) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/A9JxGJ8ALB/ea_profile.json
* 2024-06-22 02:12:54 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/A9JxGJ8ALB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-22 02:12:54 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-23 02:12:42 (7818) [[32mINFO[0m] Self-update of script version 41 requested.
* 2024-06-23 02:12:42 (7840) [[32mINFO[0m] Script is up to date.
* 2024-06-23 02:12:45 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-23 02:12:48 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-23 02:12:48 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-23 02:12:48 (6590) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-23 02:12:48 (6591) [[32mINFO[0m] 
* 2024-06-23 02:12:48 (6604) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-23 02:12:48 (6604) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-23 02:12:48 (6604) [[32mINFO[0m]               : epel extras updates
* 2024-06-23 02:12:48 (6604) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-23 02:12:48 (6604) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-23 02:12:48 (6621) [[32mINFO[0m] 
* 2024-06-23 02:12:52 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-23 02:12:52 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-23 02:12:52 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-23 02:12:52 (5773) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1uhXLQkeY6/ea_profile.json
* 2024-06-23 02:12:58 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1uhXLQkeY6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-23 02:12:58 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-24 02:12:20 (7818) [[32mINFO[0m] Self-update of script version 41 requested.
* 2024-06-24 02:12:21 (7840) [[32mINFO[0m] Script is up to date.
* 2024-06-24 02:12:23 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-24 02:12:26 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-24 02:12:26 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-24 02:12:26 (6590) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-24 02:12:26 (6591) [[32mINFO[0m] 
* 2024-06-24 02:12:26 (6604) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-24 02:12:26 (6604) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-24 02:12:26 (6604) [[32mINFO[0m]               : epel extras updates
* 2024-06-24 02:12:26 (6604) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-24 02:12:26 (6604) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-24 02:12:26 (6621) [[32mINFO[0m] 
* 2024-06-24 02:12:48 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-24 02:12:48 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-24 02:12:48 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-24 02:12:48 (5773) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/blIRBmC6QW/ea_profile.json
* 2024-06-24 02:12:54 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/blIRBmC6QW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-24 02:12:54 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-25 02:12:15 (7818) [[32mINFO[0m] Self-update of script version 41 requested.
* 2024-06-25 02:12:16 (7840) [[32mINFO[0m] Script is up to date.
* 2024-06-25 02:12:18 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-25 02:12:21 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-25 02:12:21 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-25 02:12:21 (6590) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-25 02:12:21 (6591) [[32mINFO[0m] 
* 2024-06-25 02:12:21 (6604) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-25 02:12:21 (6604) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-25 02:12:21 (6604) [[32mINFO[0m]               : epel extras updates
* 2024-06-25 02:12:21 (6604) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-25 02:12:21 (6604) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-25 02:12:21 (6621) [[32mINFO[0m] 
* 2024-06-25 02:12:24 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-25 02:12:24 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-25 02:12:24 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-25 02:12:24 (5773) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BRDiiLWkic/ea_profile.json
* 2024-06-25 02:12:29 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BRDiiLWkic/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-25 02:12:30 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-26 02:12:08 (7818) [[32mINFO[0m] Self-update of script version 41 requested.
* 2024-06-26 02:12:09 (7840) [[32mINFO[0m] Script is up to date.
* 2024-06-26 02:12:11 (787) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-26 02:12:14 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-26 02:12:14 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-26 02:12:14 (6590) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-26 02:12:14 (6591) [[32mINFO[0m] 
* 2024-06-26 02:12:14 (6604) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-26 02:12:14 (6604) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-26 02:12:14 (6604) [[32mINFO[0m]               : epel extras updates
* 2024-06-26 02:12:14 (6604) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-26 02:12:14 (6604) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-26 02:12:14 (6621) [[32mINFO[0m] 
* 2024-06-26 02:12:18 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-26 02:12:18 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-26 02:12:18 (1042) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-26 02:12:18 (5773) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QplQNGbY2I/ea_profile.json
* 2024-06-26 02:12:25 (353) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QplQNGbY2I/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775.
* 2024-06-26 02:12:25 (317) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-27 02:15:24 (7818) [[32mINFO[0m] Self-update of script version 41 requested.
* 2024-06-27 02:15:24 (7823) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-06-27 02:15:26 (7832) [[32mINFO[0m] Script update to version 43 successful.
* 2024-06-27 02:15:28 (790) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-27 02:15:31 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-27 02:15:31 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-27 02:15:31 (6737) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-27 02:15:31 (6738) [[32mINFO[0m] 
* 2024-06-27 02:15:31 (6751) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-27 02:15:31 (6751) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-27 02:15:31 (6751) [[32mINFO[0m]               : epel extras updates
* 2024-06-27 02:15:31 (6751) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-27 02:15:31 (6751) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-27 02:15:31 (6768) [[32mINFO[0m] 
* 2024-06-27 02:15:35 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-27 02:15:35 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-27 02:15:36 (1045) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-27 02:15:36 (5881) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2rkr5EXu_q/ea_profile.json
* 2024-06-27 02:15:43 (356) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2rkr5EXu_q/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5883.
* 2024-06-27 02:15:43 (320) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-28 02:12:22 (7972) [[32mINFO[0m] Self-update of script version 43 requested.
* 2024-06-28 02:12:22 (7994) [[32mINFO[0m] Script is up to date.
* 2024-06-28 02:12:24 (790) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-28 02:12:27 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-28 02:12:27 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-28 02:12:27 (6737) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-28 02:12:27 (6738) [[32mINFO[0m] 
* 2024-06-28 02:12:27 (6751) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-28 02:12:27 (6751) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-28 02:12:27 (6751) [[32mINFO[0m]               : epel extras updates
* 2024-06-28 02:12:27 (6751) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-28 02:12:27 (6751) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-28 02:12:27 (6768) [[32mINFO[0m] 
* 2024-06-28 02:12:31 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-28 02:12:31 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-28 02:12:31 (1045) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-28 02:12:31 (5881) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TSKYKmtdk0/ea_profile.json
* 2024-06-28 02:12:36 (356) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TSKYKmtdk0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5883.
* 2024-06-28 02:12:36 (320) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-28 15:46:22 (7972) [[32mINFO[0m] Self-update of script version 43 requested.
* 2024-06-28 15:46:22 (7994) [[32mINFO[0m] Script is up to date.
* 2024-06-28 15:46:25 (790) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-28 15:46:28 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-28 15:46:28 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-28 15:46:28 (6737) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-28 15:46:28 (6738) [[32mINFO[0m] 
* 2024-06-28 15:46:28 (6751) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-28 15:46:28 (6751) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-28 15:46:28 (6751) [[32mINFO[0m]               : epel extras updates
* 2024-06-28 15:46:28 (6751) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-28 15:46:28 (6751) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-28 15:46:28 (6768) [[32mINFO[0m] 
* 2024-06-28 15:46:32 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-28 15:46:32 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-28 15:46:32 (1045) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-28 15:46:32 (5881) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y1RDZwwnWA/ea_profile.json
* 2024-06-28 15:46:41 (356) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y1RDZwwnWA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5883.
* 2024-06-28 15:46:41 (320) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-29 02:12:40 (7972) [[32mINFO[0m] Self-update of script version 43 requested.
* 2024-06-29 02:12:41 (7994) [[32mINFO[0m] Script is up to date.
* 2024-06-29 02:12:43 (790) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-29 02:12:46 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-29 02:12:46 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-29 02:12:46 (6737) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-29 02:12:46 (6738) [[32mINFO[0m] 
* 2024-06-29 02:12:46 (6751) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-29 02:12:46 (6751) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-29 02:12:46 (6751) [[32mINFO[0m]               : epel extras updates
* 2024-06-29 02:12:46 (6751) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-29 02:12:46 (6751) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-29 02:12:46 (6768) [[32mINFO[0m] 
* 2024-06-29 02:12:49 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-29 02:12:49 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-29 02:12:49 (1045) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-29 02:12:49 (5881) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/p_Yofbj8s6/ea_profile.json
* 2024-06-29 02:12:55 (356) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/p_Yofbj8s6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5883.
* 2024-06-29 02:12:55 (320) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-30 02:12:35 (7972) [[32mINFO[0m] Self-update of script version 43 requested.
* 2024-06-30 02:12:36 (7994) [[32mINFO[0m] Script is up to date.
* 2024-06-30 02:12:38 (790) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-06-30 02:12:41 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-30 02:12:41 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-06-30 02:12:41 (6737) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-06-30 02:12:41 (6738) [[32mINFO[0m] 
* 2024-06-30 02:12:41 (6751) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-30 02:12:41 (6751) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-06-30 02:12:41 (6751) [[32mINFO[0m]               : epel extras updates
* 2024-06-30 02:12:41 (6751) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-06-30 02:12:41 (6751) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-06-30 02:12:41 (6768) [[32mINFO[0m] 
* 2024-06-30 02:12:45 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-06-30 02:12:45 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-06-30 02:12:45 (1045) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-30 02:12:45 (5881) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8X4U5QNukb/ea_profile.json
* 2024-06-30 02:12:50 (356) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8X4U5QNukb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5883.
* 2024-06-30 02:12:52 (320) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-01 02:12:13 (7972) [[32mINFO[0m] Self-update of script version 43 requested.
* 2024-07-01 02:12:14 (7994) [[32mINFO[0m] Script is up to date.
* 2024-07-01 02:12:16 (790) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-01 02:12:19 (1985) [[33mWARN[0m] Initial run of "yum makecache" failed: 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-07-01 02:12:19 (1986) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-01 02:12:19 (6737) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-01 02:12:19 (6738) [[32mINFO[0m] 
* 2024-07-01 02:12:19 (6751) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-01 02:12:19 (6751) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-01 02:12:19 (6751) [[32mINFO[0m]               : epel extras updates
* 2024-07-01 02:12:19 (6751) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-01 02:12:19 (6751) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-01 02:12:19 (6768) [[32mINFO[0m] 
* 2024-07-01 02:12:22 (1995) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-07-01 02:12:22 (1996) [[31mERROR[0m] 

 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
* 2024-07-01 02:12:23 (1045) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-01 02:12:23 (5881) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3MjOEHGdvd/ea_profile.json
* 2024-07-01 02:12:28 (356) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3MjOEHGdvd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5883.
* 2024-07-01 02:12:28 (320) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-02 02:12:10 (7972) [[32mINFO[0m] Self-update of script version 43 requested.
* 2024-07-02 02:12:11 (7977) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-07-02 02:12:12 (7986) [[32mINFO[0m] Script update to version 44 successful.
* 2024-07-02 02:12:14 (791) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-02 02:12:16 (1986) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-02 02:12:16 (1987) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-02 02:12:16 (6799) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-02 02:12:16 (6800) [[32mINFO[0m] 
* 2024-07-02 02:12:16 (6813) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-02 02:12:16 (6813) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-02 02:12:16 (6813) [[32mINFO[0m]               : epel extras updates
* 2024-07-02 02:12:16 (6813) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-02 02:12:16 (6813) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-02 02:12:16 (6830) [[32mINFO[0m] 
* 2024-07-02 02:12:17 (1996) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-07-02 02:12:17 (1997) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-02 02:12:18 (1046) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-02 02:12:18 (5943) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NeB5Wy1WtG/ea_profile.json
* 2024-07-02 02:12:21 (357) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NeB5Wy1WtG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5945.
* 2024-07-02 02:12:21 (321) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-03 02:12:09 (8035) [[32mINFO[0m] Self-update of script version 44 requested.
* 2024-07-03 02:12:09 (8057) [[32mINFO[0m] Script is up to date.
* 2024-07-03 02:12:11 (791) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-03 02:12:13 (1986) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-03 02:12:13 (1987) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-03 02:12:13 (6799) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-03 02:12:13 (6800) [[32mINFO[0m] 
* 2024-07-03 02:12:13 (6813) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-03 02:12:13 (6813) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-03 02:12:13 (6813) [[32mINFO[0m]               : epel extras updates
* 2024-07-03 02:12:13 (6813) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-03 02:12:13 (6813) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-03 02:12:13 (6830) [[32mINFO[0m] 
* 2024-07-03 02:12:14 (1996) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-07-03 02:12:14 (1997) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-03 02:12:14 (1046) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-03 02:12:14 (5943) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0r9iOJaEfD/ea_profile.json
* 2024-07-03 02:12:17 (357) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0r9iOJaEfD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5945.
* 2024-07-03 02:12:17 (321) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-04 02:12:05 (8035) [[32mINFO[0m] Self-update of script version 44 requested.
* 2024-07-04 02:12:11 (8040) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-07-04 02:12:12 (8049) [[32mINFO[0m] Script update to version 45 successful.
* 2024-07-04 02:12:14 (791) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-04 02:12:15 (1999) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-04 02:12:15 (2000) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-04 02:12:15 (6813) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-04 02:12:15 (6814) [[32mINFO[0m] 
* 2024-07-04 02:12:16 (6827) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-04 02:12:16 (6827) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-04 02:12:16 (6827) [[32mINFO[0m]               : epel extras updates
* 2024-07-04 02:12:16 (6827) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-04 02:12:16 (6827) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-04 02:12:16 (6844) [[32mINFO[0m] 
* 2024-07-04 02:12:17 (2009) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-07-04 02:12:17 (2010) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-04 02:12:18 (1059) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-04 02:12:18 (5957) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mr0myB7_a7/ea_profile.json
* 2024-07-04 02:12:21 (357) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mr0myB7_a7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-04 02:12:21 (321) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-05 02:12:10 (8049) [[32mINFO[0m] Self-update of script version 45 requested.
* 2024-07-05 02:12:11 (8071) [[32mINFO[0m] Script is up to date.
* 2024-07-05 02:12:13 (791) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-05 02:12:14 (1999) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-05 02:12:14 (2000) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-05 02:12:14 (6813) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-05 02:12:14 (6814) [[32mINFO[0m] 
* 2024-07-05 02:12:14 (6827) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-05 02:12:14 (6827) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-05 02:12:14 (6827) [[32mINFO[0m]               : epel extras updates
* 2024-07-05 02:12:14 (6827) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-05 02:12:14 (6827) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-05 02:12:14 (6844) [[32mINFO[0m] 
* 2024-07-05 02:12:16 (2009) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-07-05 02:12:16 (2010) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-05 02:12:16 (1059) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-05 02:12:16 (5957) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8BrYiD5ujU/ea_profile.json
* 2024-07-05 02:12:20 (357) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8BrYiD5ujU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-05 02:12:20 (321) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-05 15:46:46 (8049) [[32mINFO[0m] Self-update of script version 45 requested.
* 2024-07-05 15:46:47 (8071) [[32mINFO[0m] Script is up to date.
* 2024-07-05 15:46:49 (791) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-05 15:46:55 (1999) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-05 15:46:55 (2000) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-05 15:46:55 (6813) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-05 15:46:55 (6814) [[32mINFO[0m] 
* 2024-07-05 15:46:56 (6827) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-05 15:46:56 (6827) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-05 15:46:56 (6827) [[32mINFO[0m]               : epel extras updates
* 2024-07-05 15:46:56 (6827) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-05 15:46:56 (6827) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-05 15:46:56 (6844) [[32mINFO[0m] 
* 2024-07-05 15:46:57 (2009) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-07-05 15:46:57 (2010) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-05 15:46:57 (1059) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-05 15:46:57 (5957) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7pdgMsMZ6t/ea_profile.json
* 2024-07-05 15:47:00 (357) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7pdgMsMZ6t/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-05 15:47:00 (321) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-06 02:12:49 (8049) [[32mINFO[0m] Self-update of script version 45 requested.
* 2024-07-06 02:12:49 (8071) [[32mINFO[0m] Script is up to date.
* 2024-07-06 02:12:51 (791) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-06 02:12:53 (1999) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-06 02:12:53 (2000) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-06 02:12:53 (6813) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-06 02:12:53 (6814) [[32mINFO[0m] 
* 2024-07-06 02:12:53 (6827) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-06 02:12:53 (6827) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-06 02:12:53 (6827) [[32mINFO[0m]               : epel extras updates
* 2024-07-06 02:12:53 (6827) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-06 02:12:53 (6827) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-06 02:12:53 (6844) [[32mINFO[0m] 
* 2024-07-06 02:12:55 (2009) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-07-06 02:12:55 (2010) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-06 02:12:56 (1059) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-06 02:12:56 (5957) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sNz_yc8pI8/ea_profile.json
* 2024-07-06 02:12:59 (357) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sNz_yc8pI8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-06 02:12:59 (321) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-07 02:12:38 (8049) [[32mINFO[0m] Self-update of script version 45 requested.
* 2024-07-07 02:12:38 (8071) [[32mINFO[0m] Script is up to date.
* 2024-07-07 02:12:41 (791) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-07 02:12:42 (1999) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-07 02:12:42 (2000) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-07 02:12:42 (6813) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-07 02:12:42 (6814) [[32mINFO[0m] 
* 2024-07-07 02:12:42 (6827) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-07 02:12:42 (6827) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-07 02:12:42 (6827) [[32mINFO[0m]               : epel extras updates
* 2024-07-07 02:12:42 (6827) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-07 02:12:42 (6827) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-07 02:12:42 (6844) [[32mINFO[0m] 
* 2024-07-07 02:12:43 (2009) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-07-07 02:12:43 (2010) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-07 02:12:43 (1059) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-07 02:12:43 (5957) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ug1Sv4YTxF/ea_profile.json
* 2024-07-07 02:12:46 (357) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ug1Sv4YTxF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-07 02:12:46 (321) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-08 02:12:10 (8049) [[32mINFO[0m] Self-update of script version 45 requested.
* 2024-07-08 02:12:11 (8071) [[32mINFO[0m] Script is up to date.
* 2024-07-08 02:12:13 (791) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-08 02:12:14 (1999) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-08 02:12:14 (2000) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-08 02:12:14 (6813) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-08 02:12:14 (6814) [[32mINFO[0m] 
* 2024-07-08 02:12:14 (6827) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-08 02:12:14 (6827) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-08 02:12:14 (6827) [[32mINFO[0m]               : epel extras updates
* 2024-07-08 02:12:14 (6827) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-08 02:12:14 (6827) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-08 02:12:14 (6844) [[32mINFO[0m] 
* 2024-07-08 02:12:16 (2009) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-07-08 02:12:16 (2010) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-08 02:12:16 (1059) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-08 02:12:16 (5957) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pEDoyu1cEI/ea_profile.json
* 2024-07-08 02:12:19 (357) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pEDoyu1cEI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-08 02:12:19 (321) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-09 02:12:10 (8049) [[32mINFO[0m] Self-update of script version 45 requested.
* 2024-07-09 02:12:10 (8071) [[32mINFO[0m] Script is up to date.
* 2024-07-09 02:12:13 (791) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-09 02:12:14 (1999) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-09 02:12:14 (2000) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-09 02:12:14 (6813) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-09 02:12:14 (6814) [[32mINFO[0m] 
* 2024-07-09 02:12:14 (6827) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-09 02:12:14 (6827) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-09 02:12:14 (6827) [[32mINFO[0m]               : epel extras updates
* 2024-07-09 02:12:14 (6827) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-09 02:12:14 (6827) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-09 02:12:14 (6844) [[32mINFO[0m] 
* 2024-07-09 02:12:16 (2009) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-07-09 02:12:16 (2010) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-09 02:12:16 (1059) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-09 02:12:16 (5957) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/x92wPJNrhK/ea_profile.json
* 2024-07-09 02:12:19 (357) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/x92wPJNrhK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-09 02:12:19 (321) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-10 02:12:11 (8049) [[32mINFO[0m] Self-update of script version 45 requested.
* 2024-07-10 02:12:11 (8071) [[32mINFO[0m] Script is up to date.
* 2024-07-10 02:12:14 (791) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-10 02:12:16 (1999) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-10 02:12:16 (2000) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-10 02:12:16 (6813) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-10 02:12:16 (6814) [[32mINFO[0m] 
* 2024-07-10 02:12:16 (6827) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-10 02:12:16 (6827) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-10 02:12:16 (6827) [[32mINFO[0m]               : epel extras updates
* 2024-07-10 02:12:16 (6827) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-10 02:12:16 (6827) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-10 02:12:16 (6844) [[32mINFO[0m] 
* 2024-07-10 02:12:18 (2009) [[31mERROR[0m] yum appears to be unstable. Please address this before upgrading
* 2024-07-10 02:12:18 (2010) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-10 02:12:19 (1059) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-10 02:12:19 (5957) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cJXR1Taenv/ea_profile.json
* 2024-07-10 02:12:23 (357) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cJXR1Taenv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-10 02:12:23 (321) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-11 02:14:30 (8049) [[32mINFO[0m] Self-update of script version 45 requested.
* 2024-07-11 02:14:31 (8054) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-07-11 02:14:32 (8063) [[32mINFO[0m] Script update to version 46 successful.
* 2024-07-11 02:14:34 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-11 02:14:34 (6846) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-11 02:14:34 (6847) [[32mINFO[0m] 
* 2024-07-11 02:14:37 (6877) [[32mINFO[0m] 
* 2024-07-11 02:15:09 (2025) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-11 02:15:09 (2026) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-11 02:15:09 (6846) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-11 02:15:09 (6847) [[32mINFO[0m] 
* 2024-07-11 02:15:09 (6860) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-11 02:15:09 (6860) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-11 02:15:09 (6860) [[32mINFO[0m]               : epel extras updates
* 2024-07-11 02:15:09 (6860) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-11 02:15:09 (6860) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-11 02:15:09 (6877) [[32mINFO[0m] 
* 2024-07-11 02:15:17 (2035) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-11 02:15:17 (2036) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-11 02:15:18 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-11 02:15:18 (5988) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ly1vFgXxRu/ea_profile.json
* 2024-07-11 02:15:24 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ly1vFgXxRu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-11 02:15:24 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-12 02:12:11 (8126) [[32mINFO[0m] Self-update of script version 46 requested.
* 2024-07-12 02:12:11 (8131) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-07-12 02:12:12 (8140) [[32mINFO[0m] Script update to version 47 successful.
* 2024-07-12 02:12:15 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-12 02:12:15 (6848) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-12 02:12:15 (6849) [[32mINFO[0m] 
* 2024-07-12 02:12:17 (6879) [[32mINFO[0m] 
* 2024-07-12 02:12:20 (2025) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-12 02:12:20 (2026) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-12 02:12:20 (6848) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-12 02:12:20 (6849) [[32mINFO[0m] 
* 2024-07-12 02:12:20 (6862) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-12 02:12:21 (6862) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-12 02:12:21 (6862) [[32mINFO[0m]               : epel extras updates
* 2024-07-12 02:12:21 (6862) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-12 02:12:21 (6862) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-12 02:12:21 (6879) [[32mINFO[0m] 
* 2024-07-12 02:12:23 (2035) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-12 02:12:23 (2036) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-12 02:12:24 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-12 02:12:24 (5990) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/b3LJHYRRN0/ea_profile.json
* 2024-07-12 02:12:32 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/b3LJHYRRN0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-12 02:12:32 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-12 15:46:10 (8128) [[32mINFO[0m] Self-update of script version 47 requested.
* 2024-07-12 15:46:10 (8150) [[32mINFO[0m] Script is up to date.
* 2024-07-12 15:46:12 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-12 15:46:12 (6848) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-12 15:46:12 (6849) [[32mINFO[0m] 
* 2024-07-12 15:46:28 (6879) [[32mINFO[0m] 
* 2024-07-12 15:46:46 (2025) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-12 15:46:46 (2026) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-12 15:46:46 (6848) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-12 15:46:46 (6849) [[32mINFO[0m] 
* 2024-07-12 15:46:46 (6862) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-12 15:46:46 (6862) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-12 15:46:46 (6862) [[32mINFO[0m]               : epel extras updates
* 2024-07-12 15:46:46 (6862) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-12 15:46:46 (6862) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-12 15:46:46 (6879) [[32mINFO[0m] 
* 2024-07-12 15:46:47 (2035) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-12 15:46:47 (2036) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-12 15:46:48 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-12 15:46:48 (5990) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RLhSy4ENzX/ea_profile.json
* 2024-07-12 15:47:06 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RLhSy4ENzX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-12 15:47:06 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-13 02:12:34 (8128) [[32mINFO[0m] Self-update of script version 47 requested.
* 2024-07-13 02:12:35 (8150) [[32mINFO[0m] Script is up to date.
* 2024-07-13 02:12:37 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-13 02:12:37 (6848) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-13 02:12:37 (6849) [[32mINFO[0m] 
* 2024-07-13 02:12:39 (6879) [[32mINFO[0m] 
* 2024-07-13 02:12:42 (2025) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-13 02:12:42 (2026) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-13 02:12:42 (6848) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-13 02:12:42 (6849) [[32mINFO[0m] 
* 2024-07-13 02:12:42 (6862) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-13 02:12:42 (6862) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-13 02:12:42 (6862) [[32mINFO[0m]               : epel extras updates
* 2024-07-13 02:12:42 (6862) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-13 02:12:42 (6862) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-13 02:12:42 (6879) [[32mINFO[0m] 
* 2024-07-13 02:12:44 (2035) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:44 (2036) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-13 02:12:44 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-13 02:12:44 (5990) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rXEwFAz3p7/ea_profile.json
* 2024-07-13 02:12:48 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rXEwFAz3p7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-13 02:12:48 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-14 02:12:38 (8128) [[32mINFO[0m] Self-update of script version 47 requested.
* 2024-07-14 02:12:38 (8150) [[32mINFO[0m] Script is up to date.
* 2024-07-14 02:12:40 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-14 02:12:40 (6848) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-14 02:12:40 (6849) [[32mINFO[0m] 
* 2024-07-14 02:12:42 (6879) [[32mINFO[0m] 
* 2024-07-14 02:12:45 (2025) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-14 02:12:45 (2026) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-14 02:12:45 (6848) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-14 02:12:45 (6849) [[32mINFO[0m] 
* 2024-07-14 02:12:45 (6862) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-14 02:12:45 (6862) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-14 02:12:45 (6862) [[32mINFO[0m]               : epel extras updates
* 2024-07-14 02:12:45 (6862) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-14 02:12:45 (6862) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-14 02:12:45 (6879) [[32mINFO[0m] 
* 2024-07-14 02:12:47 (2035) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:47 (2036) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-14 02:12:47 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-14 02:12:47 (5990) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6oeDyKzZ_z/ea_profile.json
* 2024-07-14 02:12:50 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6oeDyKzZ_z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-14 02:12:50 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-15 02:12:24 (8128) [[32mINFO[0m] Self-update of script version 47 requested.
* 2024-07-15 02:12:25 (8150) [[32mINFO[0m] Script is up to date.
* 2024-07-15 02:12:27 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-15 02:12:27 (6848) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-15 02:12:27 (6849) [[32mINFO[0m] 
* 2024-07-15 02:12:29 (6879) [[32mINFO[0m] 
* 2024-07-15 02:12:32 (2025) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-15 02:12:32 (2026) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-15 02:12:32 (6848) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-15 02:12:32 (6849) [[32mINFO[0m] 
* 2024-07-15 02:12:32 (6862) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-15 02:12:32 (6862) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-15 02:12:32 (6862) [[32mINFO[0m]               : epel extras updates
* 2024-07-15 02:12:32 (6862) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-15 02:12:32 (6862) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-15 02:12:32 (6879) [[32mINFO[0m] 
* 2024-07-15 02:12:33 (2035) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:33 (2036) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-15 02:12:34 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-15 02:12:34 (5990) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rdtscrqR6D/ea_profile.json
* 2024-07-15 02:12:36 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rdtscrqR6D/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-15 02:12:36 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-16 02:12:08 (8128) [[32mINFO[0m] Self-update of script version 47 requested.
* 2024-07-16 02:12:08 (8150) [[32mINFO[0m] Script is up to date.
* 2024-07-16 02:12:11 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-16 02:12:11 (6848) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-16 02:12:11 (6849) [[32mINFO[0m] 
* 2024-07-16 02:12:13 (6879) [[32mINFO[0m] 
* 2024-07-16 02:12:18 (2025) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-16 02:12:18 (2026) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-16 02:12:18 (6848) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-16 02:12:18 (6849) [[32mINFO[0m] 
* 2024-07-16 02:12:18 (6862) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-16 02:12:18 (6862) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-16 02:12:18 (6862) [[32mINFO[0m]               : epel extras updates
* 2024-07-16 02:12:18 (6862) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-16 02:12:18 (6862) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-16 02:12:18 (6879) [[32mINFO[0m] 
* 2024-07-16 02:12:20 (2035) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:20 (2036) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-16 02:12:21 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-16 02:12:21 (5990) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UYZlwMdvxR/ea_profile.json
* 2024-07-16 02:12:25 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UYZlwMdvxR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-16 02:12:25 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-17 02:12:08 (8128) [[32mINFO[0m] Self-update of script version 47 requested.
* 2024-07-17 02:12:08 (8133) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-07-17 02:12:09 (8142) [[32mINFO[0m] Script update to version 48 successful.
* 2024-07-17 02:12:11 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-17 02:12:11 (6846) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-17 02:12:11 (6847) [[32mINFO[0m] 
* 2024-07-17 02:12:15 (6877) [[32mINFO[0m] 
* 2024-07-17 02:12:20 (2025) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-17 02:12:20 (2026) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-17 02:12:20 (6846) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-17 02:12:20 (6847) [[32mINFO[0m] 
* 2024-07-17 02:12:20 (6860) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-17 02:12:20 (6860) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-17 02:12:20 (6860) [[32mINFO[0m]               : epel extras updates
* 2024-07-17 02:12:20 (6860) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-17 02:12:20 (6860) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-17 02:12:20 (6877) [[32mINFO[0m] 
* 2024-07-17 02:12:23 (2035) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-17 02:12:23 (2036) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-17 02:12:24 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-17 02:12:26 (5988) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ag1407JvjG/ea_profile.json
* 2024-07-17 02:12:32 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ag1407JvjG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-17 02:12:32 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-18 02:12:12 (8126) [[32mINFO[0m] Self-update of script version 48 requested.
* 2024-07-18 02:12:12 (8148) [[32mINFO[0m] Script is up to date.
* 2024-07-18 02:12:14 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-18 02:12:14 (6846) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-18 02:12:14 (6847) [[32mINFO[0m] 
* 2024-07-18 02:12:16 (6877) [[32mINFO[0m] 
* 2024-07-18 02:12:18 (2025) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-18 02:12:18 (2026) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-18 02:12:18 (6846) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-18 02:12:18 (6847) [[32mINFO[0m] 
* 2024-07-18 02:12:18 (6860) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-18 02:12:18 (6860) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-18 02:12:18 (6860) [[32mINFO[0m]               : epel extras updates
* 2024-07-18 02:12:18 (6860) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-18 02:12:18 (6860) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-18 02:12:18 (6877) [[32mINFO[0m] 
* 2024-07-18 02:12:19 (2035) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:19 (2036) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-18 02:12:20 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-18 02:12:20 (5988) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fiNXig51a0/ea_profile.json
* 2024-07-18 02:12:23 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fiNXig51a0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-18 02:12:23 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-19 02:12:14 (8126) [[32mINFO[0m] Self-update of script version 48 requested.
* 2024-07-19 02:12:15 (8148) [[32mINFO[0m] Script is up to date.
* 2024-07-19 02:12:17 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-19 02:12:17 (6846) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-19 02:12:17 (6847) [[32mINFO[0m] 
* 2024-07-19 02:12:19 (6877) [[32mINFO[0m] 
* 2024-07-19 02:12:23 (2025) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-19 02:12:23 (2026) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-19 02:12:23 (6846) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-19 02:12:23 (6847) [[32mINFO[0m] 
* 2024-07-19 02:12:23 (6860) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-19 02:12:23 (6860) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-19 02:12:23 (6860) [[32mINFO[0m]               : epel extras updates
* 2024-07-19 02:12:23 (6860) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-19 02:12:23 (6860) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-19 02:12:23 (6877) [[32mINFO[0m] 
* 2024-07-19 02:12:25 (2035) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:25 (2036) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-19 02:12:26 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-19 02:12:26 (5988) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/n4czIedM8d/ea_profile.json
* 2024-07-19 02:12:30 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/n4czIedM8d/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-19 02:12:30 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-20 02:12:46 (8126) [[32mINFO[0m] Self-update of script version 48 requested.
* 2024-07-20 02:12:47 (8148) [[32mINFO[0m] Script is up to date.
* 2024-07-20 02:12:49 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-20 02:12:49 (6846) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-20 02:12:49 (6847) [[32mINFO[0m] 
* 2024-07-20 02:12:50 (6877) [[32mINFO[0m] 
* 2024-07-20 02:13:10 (2025) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-20 02:13:10 (2026) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-20 02:13:10 (6846) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-20 02:13:10 (6847) [[32mINFO[0m] 
* 2024-07-20 02:13:10 (6860) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-20 02:13:10 (6860) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-20 02:13:10 (6860) [[32mINFO[0m]               : epel extras updates
* 2024-07-20 02:13:10 (6860) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-20 02:13:10 (6860) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-20 02:13:10 (6877) [[32mINFO[0m] 
* 2024-07-20 02:13:11 (2035) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:13:11 (2036) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-20 02:13:12 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-20 02:13:12 (5988) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RGBGR7xZ68/ea_profile.json
* 2024-07-20 02:13:15 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RGBGR7xZ68/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-20 02:13:15 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-21 02:12:29 (8126) [[32mINFO[0m] Self-update of script version 48 requested.
* 2024-07-21 02:12:30 (8148) [[32mINFO[0m] Script is up to date.
* 2024-07-21 02:12:31 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-21 02:12:31 (6846) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-21 02:12:31 (6847) [[32mINFO[0m] 
* 2024-07-21 02:12:32 (6877) [[32mINFO[0m] 
* 2024-07-21 02:12:34 (2025) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-21 02:12:34 (2026) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-21 02:12:34 (6846) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-21 02:12:34 (6847) [[32mINFO[0m] 
* 2024-07-21 02:12:35 (6860) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-21 02:12:35 (6860) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-21 02:12:35 (6860) [[32mINFO[0m]               : epel extras updates
* 2024-07-21 02:12:35 (6860) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-21 02:12:35 (6860) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-21 02:12:35 (6877) [[32mINFO[0m] 
* 2024-07-21 02:12:35 (2035) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-21 02:12:35 (2036) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-21 02:12:36 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-21 02:12:36 (5988) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ALKFT4WKxz/ea_profile.json
* 2024-07-21 02:12:38 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ALKFT4WKxz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-21 02:12:38 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-22 02:12:07 (8126) [[32mINFO[0m] Self-update of script version 48 requested.
* 2024-07-22 02:12:08 (8148) [[32mINFO[0m] Script is up to date.
* 2024-07-22 02:12:09 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-22 02:12:09 (6846) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-22 02:12:09 (6847) [[32mINFO[0m] 
* 2024-07-22 02:12:11 (6877) [[32mINFO[0m] 
* 2024-07-22 02:12:13 (2025) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-22 02:12:13 (2026) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-22 02:12:13 (6846) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-22 02:12:13 (6847) [[32mINFO[0m] 
* 2024-07-22 02:12:14 (6860) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-22 02:12:14 (6860) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-22 02:12:14 (6860) [[32mINFO[0m]               : epel extras updates
* 2024-07-22 02:12:14 (6860) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-22 02:12:14 (6860) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-22 02:12:14 (6877) [[32mINFO[0m] 
* 2024-07-22 02:12:15 (2035) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-22 02:12:15 (2036) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-22 02:12:15 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-22 02:12:15 (5988) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/a9Y5IV6HE1/ea_profile.json
* 2024-07-22 02:12:19 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/a9Y5IV6HE1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-22 02:12:19 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-23 02:12:08 (8126) [[32mINFO[0m] Self-update of script version 48 requested.
* 2024-07-23 02:12:09 (8148) [[32mINFO[0m] Script is up to date.
* 2024-07-23 02:12:11 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-23 02:12:11 (6846) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-23 02:12:11 (6847) [[32mINFO[0m] 
* 2024-07-23 02:12:12 (6877) [[32mINFO[0m] 
* 2024-07-23 02:12:15 (2025) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-23 02:12:15 (2026) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-23 02:12:15 (6846) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-23 02:12:15 (6847) [[32mINFO[0m] 
* 2024-07-23 02:12:15 (6860) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-23 02:12:15 (6860) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-23 02:12:15 (6860) [[32mINFO[0m]               : epel extras updates
* 2024-07-23 02:12:15 (6860) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-23 02:12:15 (6860) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-23 02:12:15 (6877) [[32mINFO[0m] 
* 2024-07-23 02:12:17 (2035) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-23 02:12:17 (2036) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-23 02:12:17 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-23 02:12:17 (5988) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VM3eV1mFKy/ea_profile.json
* 2024-07-23 02:12:20 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VM3eV1mFKy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-23 02:12:20 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-24 02:12:06 (8126) [[32mINFO[0m] Self-update of script version 48 requested.
* 2024-07-24 02:12:06 (8148) [[32mINFO[0m] Script is up to date.
* 2024-07-24 02:12:08 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-24 02:12:08 (6846) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-24 02:12:08 (6847) [[32mINFO[0m] 
* 2024-07-24 02:12:09 (6877) [[32mINFO[0m] 
* 2024-07-24 02:12:11 (2025) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-24 02:12:11 (2026) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-24 02:12:11 (6846) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-24 02:12:11 (6847) [[32mINFO[0m] 
* 2024-07-24 02:12:11 (6860) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-24 02:12:11 (6860) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-24 02:12:11 (6860) [[32mINFO[0m]               : epel extras updates
* 2024-07-24 02:12:11 (6860) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-24 02:12:11 (6860) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-24 02:12:11 (6877) [[32mINFO[0m] 
* 2024-07-24 02:12:11 (2035) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:11 (2036) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-24 02:12:12 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-24 02:12:12 (5988) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FZ0JKyWtZr/ea_profile.json
* 2024-07-24 02:12:14 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FZ0JKyWtZr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-24 02:12:14 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-25 02:12:11 (8126) [[32mINFO[0m] Self-update of script version 48 requested.
* 2024-07-25 02:12:11 (8131) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-07-25 02:12:12 (8140) [[32mINFO[0m] Script update to version 49 successful.
* 2024-07-25 02:12:14 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-25 02:12:14 (6907) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-25 02:12:14 (6908) [[32mINFO[0m] 
* 2024-07-25 02:12:20 (6938) [[32mINFO[0m] 
* 2024-07-25 02:12:25 (2047) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-25 02:12:25 (2048) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-25 02:12:25 (6907) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-25 02:12:25 (6908) [[32mINFO[0m] 
* 2024-07-25 02:12:25 (6921) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-25 02:12:25 (6921) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-25 02:12:25 (6921) [[32mINFO[0m]               : epel extras updates
* 2024-07-25 02:12:25 (6921) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-25 02:12:25 (6921) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-25 02:12:25 (6938) [[32mINFO[0m] 
* 2024-07-25 02:12:30 (2057) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-25 02:12:30 (2058) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-25 02:12:30 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-25 02:12:30 (6049) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/d_nJamxJno/ea_profile.json
* 2024-07-25 02:12:36 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/d_nJamxJno/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-25 02:12:36 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-26 02:12:06 (8187) [[32mINFO[0m] Self-update of script version 49 requested.
* 2024-07-26 02:12:07 (8209) [[32mINFO[0m] Script is up to date.
* 2024-07-26 02:12:09 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-26 02:12:09 (6907) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-26 02:12:09 (6908) [[32mINFO[0m] 
* 2024-07-26 02:12:11 (6938) [[32mINFO[0m] 
* 2024-07-26 02:12:15 (2047) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-26 02:12:15 (2048) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-26 02:12:15 (6907) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-26 02:12:15 (6908) [[32mINFO[0m] 
* 2024-07-26 02:12:15 (6921) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-26 02:12:15 (6921) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-26 02:12:15 (6921) [[32mINFO[0m]               : epel extras updates
* 2024-07-26 02:12:15 (6921) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-26 02:12:15 (6921) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-26 02:12:15 (6938) [[32mINFO[0m] 
* 2024-07-26 02:12:20 (2057) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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 02:12:20 (2058) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-26 02:12:20 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-26 02:12:20 (6049) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ejYy3gV5tK/ea_profile.json
* 2024-07-26 02:12:25 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ejYy3gV5tK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-26 02:12:25 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-26 15:46:08 (8187) [[32mINFO[0m] Self-update of script version 49 requested.
* 2024-07-26 15:46:08 (8209) [[32mINFO[0m] Script is up to date.
* 2024-07-26 15:46:10 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-26 15:46:10 (6907) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-26 15:46:10 (6908) [[32mINFO[0m] 
* 2024-07-26 15:46:12 (6938) [[32mINFO[0m] 
* 2024-07-26 15:46:14 (2047) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-26 15:46:14 (2048) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-26 15:46:14 (6907) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-26 15:46:14 (6908) [[32mINFO[0m] 
* 2024-07-26 15:46:14 (6921) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-26 15:46:14 (6921) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-26 15:46:14 (6921) [[32mINFO[0m]               : epel extras updates
* 2024-07-26 15:46:14 (6921) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-26 15:46:14 (6921) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-26 15:46:14 (6938) [[32mINFO[0m] 
* 2024-07-26 15:46:16 (2057) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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 15:46:16 (2058) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-26 15:46:16 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-26 15:46:16 (6049) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UqydcauvBT/ea_profile.json
* 2024-07-26 15:46:19 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UqydcauvBT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-26 15:46:19 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-27 02:12:33 (8187) [[32mINFO[0m] Self-update of script version 49 requested.
* 2024-07-27 02:12:34 (8209) [[32mINFO[0m] Script is up to date.
* 2024-07-27 02:12:35 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-27 02:12:35 (6907) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-27 02:12:35 (6908) [[32mINFO[0m] 
* 2024-07-27 02:12:38 (6938) [[32mINFO[0m] 
* 2024-07-27 02:12:41 (2047) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-27 02:12:41 (2048) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-27 02:12:41 (6907) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-27 02:12:41 (6908) [[32mINFO[0m] 
* 2024-07-27 02:12:41 (6921) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-27 02:12:42 (6921) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-27 02:12:42 (6921) [[32mINFO[0m]               : epel extras updates
* 2024-07-27 02:12:42 (6921) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-27 02:12:42 (6921) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-27 02:12:42 (6938) [[32mINFO[0m] 
* 2024-07-27 02:12:44 (2057) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-27 02:12:44 (2058) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-27 02:12:44 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-27 02:12:44 (6049) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/18nXJAs8tx/ea_profile.json
* 2024-07-27 02:12:48 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/18nXJAs8tx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-27 02:12:48 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-28 02:12:37 (8187) [[32mINFO[0m] Self-update of script version 49 requested.
* 2024-07-28 02:12:37 (8209) [[32mINFO[0m] Script is up to date.
* 2024-07-28 02:12:39 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-28 02:12:39 (6907) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-28 02:12:39 (6908) [[32mINFO[0m] 
* 2024-07-28 02:12:40 (6938) [[32mINFO[0m] 
* 2024-07-28 02:12:43 (2047) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-28 02:12:43 (2048) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-28 02:12:43 (6907) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-28 02:12:43 (6908) [[32mINFO[0m] 
* 2024-07-28 02:12:43 (6921) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-28 02:12:43 (6921) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-28 02:12:43 (6921) [[32mINFO[0m]               : epel extras updates
* 2024-07-28 02:12:43 (6921) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-28 02:12:43 (6921) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-28 02:12:43 (6938) [[32mINFO[0m] 
* 2024-07-28 02:12:44 (2057) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-28 02:12:44 (2058) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-28 02:12:45 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-28 02:12:45 (6049) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WCnboQzMyX/ea_profile.json
* 2024-07-28 02:12:48 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WCnboQzMyX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-28 02:12:48 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-29 02:12:09 (8187) [[32mINFO[0m] Self-update of script version 49 requested.
* 2024-07-29 02:12:09 (8209) [[32mINFO[0m] Script is up to date.
* 2024-07-29 02:12:11 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-29 02:12:11 (6907) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-29 02:12:11 (6908) [[32mINFO[0m] 
* 2024-07-29 02:12:14 (6938) [[32mINFO[0m] 
* 2024-07-29 02:12:18 (2047) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-29 02:12:18 (2048) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-29 02:12:18 (6907) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-29 02:12:18 (6908) [[32mINFO[0m] 
* 2024-07-29 02:12:18 (6921) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-29 02:12:18 (6921) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-29 02:12:18 (6921) [[32mINFO[0m]               : epel extras updates
* 2024-07-29 02:12:18 (6921) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-29 02:12:18 (6921) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-29 02:12:18 (6938) [[32mINFO[0m] 
* 2024-07-29 02:12:20 (2057) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-29 02:12:20 (2058) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-29 02:12:21 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-29 02:12:21 (6049) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vmmCBqOjD3/ea_profile.json
* 2024-07-29 02:12:26 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vmmCBqOjD3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-29 02:12:26 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-30 02:12:05 (8187) [[32mINFO[0m] Self-update of script version 49 requested.
* 2024-07-30 02:12:05 (8209) [[32mINFO[0m] Script is up to date.
* 2024-07-30 02:12:07 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-30 02:12:07 (6907) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-30 02:12:07 (6908) [[32mINFO[0m] 
* 2024-07-30 02:12:08 (6938) [[32mINFO[0m] 
* 2024-07-30 02:12:10 (2047) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-30 02:12:10 (2048) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-30 02:12:10 (6907) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-30 02:12:10 (6908) [[32mINFO[0m] 
* 2024-07-30 02:12:10 (6921) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-30 02:12:10 (6921) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-30 02:12:10 (6921) [[32mINFO[0m]               : epel extras updates
* 2024-07-30 02:12:10 (6921) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-30 02:12:10 (6921) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-30 02:12:10 (6938) [[32mINFO[0m] 
* 2024-07-30 02:12:11 (2057) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-30 02:12:11 (2058) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-30 02:12:12 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-30 02:12:12 (6049) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OyhU7GJd2C/ea_profile.json
* 2024-07-30 02:12:14 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OyhU7GJd2C/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-30 02:12:14 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-31 02:12:04 (8187) [[32mINFO[0m] Self-update of script version 49 requested.
* 2024-07-31 02:12:04 (8209) [[32mINFO[0m] Script is up to date.
* 2024-07-31 02:12:06 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-07-31 02:12:06 (6907) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-07-31 02:12:06 (6908) [[32mINFO[0m] 
* 2024-07-31 02:12:07 (6938) [[32mINFO[0m] 
* 2024-07-31 02:12:10 (2047) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-31 02:12:10 (2048) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-07-31 02:12:10 (6907) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-07-31 02:12:10 (6908) [[32mINFO[0m] 
* 2024-07-31 02:12:10 (6921) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-31 02:12:10 (6921) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-07-31 02:12:10 (6921) [[32mINFO[0m]               : epel extras updates
* 2024-07-31 02:12:10 (6921) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-07-31 02:12:10 (6921) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-07-31 02:12:10 (6938) [[32mINFO[0m] 
* 2024-07-31 02:12:11 (2057) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-31 02:12:11 (2058) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-07-31 02:12:11 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-31 02:12:11 (6049) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/d3kWeBbSVQ/ea_profile.json
* 2024-07-31 02:12:14 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/d3kWeBbSVQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-31 02:12:14 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-01 02:12:04 (8187) [[32mINFO[0m] Self-update of script version 49 requested.
* 2024-08-01 02:12:05 (8209) [[32mINFO[0m] Script is up to date.
* 2024-08-01 02:12:07 (808) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-01 02:12:07 (6907) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-01 02:12:07 (6908) [[32mINFO[0m] 
* 2024-08-01 02:12:08 (6938) [[32mINFO[0m] 
* 2024-08-01 02:12:11 (2047) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-01 02:12:11 (2048) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-01 02:12:11 (6907) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-01 02:12:11 (6908) [[32mINFO[0m] 
* 2024-08-01 02:12:11 (6921) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-01 02:12:11 (6921) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-01 02:12:11 (6921) [[32mINFO[0m]               : epel extras updates
* 2024-08-01 02:12:11 (6921) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-01 02:12:11 (6921) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-01 02:12:11 (6938) [[32mINFO[0m] 
* 2024-08-01 02:12:12 (2057) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-01 02:12:12 (2058) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-01 02:12:13 (1063) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-01 02:12:13 (6049) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7YxtovULAW/ea_profile.json
* 2024-08-01 02:12:16 (374) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7YxtovULAW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-08-01 02:12:16 (338) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-02 02:13:15 (8187) [[32mINFO[0m] Self-update of script version 49 requested.
* 2024-08-02 02:13:15 (8192) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-08-02 02:13:17 (8201) [[32mINFO[0m] Script update to version 50 successful.
* 2024-08-02 02:13:18 (820) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-02 02:13:18 (7163) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-02 02:13:18 (7164) [[32mINFO[0m] 
* 2024-08-02 02:13:21 (2059) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-02 02:13:21 (2060) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-02 02:13:21 (7163) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-02 02:13:21 (7164) [[32mINFO[0m] 
* 2024-08-02 02:13:21 (7177) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-02 02:13:22 (7177) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-02 02:13:22 (7177) [[32mINFO[0m]               : epel extras updates
* 2024-08-02 02:13:22 (7177) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-02 02:13:22 (7177) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-02 02:13:22 (7194) [[32mINFO[0m] 
* 2024-08-02 02:13:22 (2069) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-02 02:13:22 (2070) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-02 02:13:22 (1075) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-02 02:13:22 (6305) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WSw653LTqT/ea_profile.json
* 2024-08-02 02:13:25 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WSw653LTqT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-02 02:13:25 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-02 16:04:05 (8474) [[32mINFO[0m] Self-update of script version 50 requested.
* 2024-08-02 16:04:05 (8496) [[32mINFO[0m] Script is up to date.
* 2024-08-02 16:04:07 (820) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-02 16:04:07 (7163) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-02 16:04:07 (7164) [[32mINFO[0m] 
* 2024-08-02 16:04:15 (2059) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-02 16:04:15 (2060) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-02 16:04:15 (7163) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-02 16:04:15 (7164) [[32mINFO[0m] 
* 2024-08-02 16:04:15 (7177) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-02 16:04:16 (7177) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-02 16:04:16 (7177) [[32mINFO[0m]               : epel extras updates
* 2024-08-02 16:04:16 (7177) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-02 16:04:16 (7177) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-02 16:04:16 (7194) [[32mINFO[0m] 
* 2024-08-02 16:04:19 (2069) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-02 16:04:19 (2070) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-02 16:04:19 (1075) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-02 16:04:19 (6305) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/i_zkErfOzB/ea_profile.json
* 2024-08-02 16:04:25 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/i_zkErfOzB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-02 16:04:25 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-03 02:12:30 (8474) [[32mINFO[0m] Self-update of script version 50 requested.
* 2024-08-03 02:12:31 (8496) [[32mINFO[0m] Script is up to date.
* 2024-08-03 02:12:33 (820) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-03 02:12:33 (7163) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-03 02:12:33 (7164) [[32mINFO[0m] 
* 2024-08-03 02:12:36 (2059) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-03 02:12:36 (2060) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-03 02:12:36 (7163) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-03 02:12:36 (7164) [[32mINFO[0m] 
* 2024-08-03 02:12:36 (7177) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-03 02:12:37 (7177) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-03 02:12:37 (7177) [[32mINFO[0m]               : epel extras updates
* 2024-08-03 02:12:37 (7177) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-03 02:12:37 (7177) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-03 02:12:37 (7194) [[32mINFO[0m] 
* 2024-08-03 02:12:38 (2069) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-03 02:12:38 (2070) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-03 02:12:38 (1075) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-03 02:12:38 (6305) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LYj1j7HVZd/ea_profile.json
* 2024-08-03 02:12:41 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LYj1j7HVZd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-03 02:12:41 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-04 02:12:34 (8474) [[32mINFO[0m] Self-update of script version 50 requested.
* 2024-08-04 02:12:34 (8496) [[32mINFO[0m] Script is up to date.
* 2024-08-04 02:12:36 (820) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-04 02:12:36 (7163) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-04 02:12:36 (7164) [[32mINFO[0m] 
* 2024-08-04 02:12:39 (2059) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-04 02:12:39 (2060) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-04 02:12:39 (7163) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-04 02:12:39 (7164) [[32mINFO[0m] 
* 2024-08-04 02:12:39 (7177) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-04 02:12:39 (7177) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-04 02:12:39 (7177) [[32mINFO[0m]               : epel extras updates
* 2024-08-04 02:12:39 (7177) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-04 02:12:39 (7177) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-04 02:12:39 (7194) [[32mINFO[0m] 
* 2024-08-04 02:12:40 (2069) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-04 02:12:40 (2070) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-04 02:12:40 (1075) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-04 02:12:40 (6305) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lYlmEOR3Z2/ea_profile.json
* 2024-08-04 02:12:43 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lYlmEOR3Z2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-04 02:12:43 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-05 02:12:09 (8474) [[32mINFO[0m] Self-update of script version 50 requested.
* 2024-08-05 02:12:10 (8496) [[32mINFO[0m] Script is up to date.
* 2024-08-05 02:12:12 (820) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-05 02:12:12 (7163) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-05 02:12:12 (7164) [[32mINFO[0m] 
* 2024-08-05 02:12:16 (2059) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-05 02:12:16 (2060) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-05 02:12:16 (7163) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-05 02:12:16 (7164) [[32mINFO[0m] 
* 2024-08-05 02:12:16 (7177) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-05 02:12:16 (7177) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-05 02:12:16 (7177) [[32mINFO[0m]               : epel extras updates
* 2024-08-05 02:12:16 (7177) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-05 02:12:16 (7177) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-05 02:12:16 (7194) [[32mINFO[0m] 
* 2024-08-05 02:12:17 (2069) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-05 02:12:17 (2070) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-05 02:12:18 (1075) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-05 02:12:18 (6305) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jjXZAH_rQ6/ea_profile.json
* 2024-08-05 02:12:21 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jjXZAH_rQ6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-05 02:12:21 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-06 02:12:06 (8474) [[32mINFO[0m] Self-update of script version 50 requested.
* 2024-08-06 02:12:07 (8496) [[32mINFO[0m] Script is up to date.
* 2024-08-06 02:12:08 (820) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-06 02:12:08 (7163) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-06 02:12:08 (7164) [[32mINFO[0m] 
* 2024-08-06 02:12:12 (2059) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-06 02:12:12 (2060) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-06 02:12:12 (7163) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-06 02:12:12 (7164) [[32mINFO[0m] 
* 2024-08-06 02:12:12 (7177) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-06 02:12:12 (7177) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-06 02:12:12 (7177) [[32mINFO[0m]               : epel extras updates
* 2024-08-06 02:12:12 (7177) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-06 02:12:12 (7177) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-06 02:12:12 (7194) [[32mINFO[0m] 
* 2024-08-06 02:12:13 (2069) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-06 02:12:13 (2070) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-06 02:12:13 (1075) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-06 02:12:13 (6305) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TMkVZKj1Dh/ea_profile.json
* 2024-08-06 02:12:15 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TMkVZKj1Dh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-06 02:12:15 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-07 02:12:04 (8474) [[32mINFO[0m] Self-update of script version 50 requested.
* 2024-08-07 02:12:05 (8496) [[32mINFO[0m] Script is up to date.
* 2024-08-07 02:12:07 (820) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-07 02:12:07 (7163) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-07 02:12:07 (7164) [[32mINFO[0m] 
* 2024-08-07 02:12:12 (2059) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-07 02:12:12 (2060) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-07 02:12:12 (7163) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-07 02:12:12 (7164) [[32mINFO[0m] 
* 2024-08-07 02:12:12 (7177) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-07 02:12:13 (7177) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-07 02:12:13 (7177) [[32mINFO[0m]               : epel extras updates
* 2024-08-07 02:12:13 (7177) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-07 02:12:13 (7177) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-07 02:12:13 (7194) [[32mINFO[0m] 
* 2024-08-07 02:12:15 (2069) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-07 02:12:15 (2070) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-07 02:12:15 (1075) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-07 02:12:15 (6305) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ssrgXYZyDG/ea_profile.json
* 2024-08-07 02:12:19 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ssrgXYZyDG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-07 02:12:19 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-08 02:12:15 (8474) [[32mINFO[0m] Self-update of script version 50 requested.
* 2024-08-08 02:12:15 (8479) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-08-08 02:12:16 (8488) [[32mINFO[0m] Script update to version 51 successful.
* 2024-08-08 02:12:18 (803) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-08 02:12:18 (7323) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-08 02:12:18 (7324) [[32mINFO[0m] 
* 2024-08-08 02:12:22 (2029) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-08 02:12:22 (2030) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-08 02:12:22 (7323) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-08 02:12:22 (7324) [[32mINFO[0m] 
* 2024-08-08 02:12:22 (7337) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-08 02:12:22 (7337) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-08 02:12:22 (7337) [[32mINFO[0m]               : epel extras updates
* 2024-08-08 02:12:22 (7337) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-08 02:12:22 (7337) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-08 02:12:22 (7354) [[32mINFO[0m] 
* 2024-08-08 02:12:24 (2039) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-08 02:12:24 (2040) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-08 02:12:24 (1058) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-08 02:12:24 (6442) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0RinNkfnXT/ea_profile.json
* 2024-08-08 02:12:27 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0RinNkfnXT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-08 02:12:27 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-09 02:13:07 (8642) [[32mINFO[0m] Self-update of script version 51 requested.
* 2024-08-09 02:13:07 (8664) [[32mINFO[0m] Script is up to date.
* 2024-08-09 02:13:09 (803) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-09 02:13:09 (7323) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-09 02:13:09 (7324) [[32mINFO[0m] 
* 2024-08-09 02:13:14 (2029) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-09 02:13:14 (2030) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-09 02:13:14 (7323) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-09 02:13:14 (7324) [[32mINFO[0m] 
* 2024-08-09 02:13:14 (7337) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-09 02:13:15 (7337) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-09 02:13:15 (7337) [[32mINFO[0m]               : epel extras updates
* 2024-08-09 02:13:15 (7337) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-09 02:13:15 (7337) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-09 02:13:15 (7354) [[32mINFO[0m] 
* 2024-08-09 02:13:16 (2039) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-09 02:13:16 (2040) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-09 02:13:16 (1058) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-09 02:13:16 (6442) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5m8c8obCcS/ea_profile.json
* 2024-08-09 02:13:20 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5m8c8obCcS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-09 02:13:20 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-09 15:46:43 (8642) [[32mINFO[0m] Self-update of script version 51 requested.
* 2024-08-09 15:46:44 (8664) [[32mINFO[0m] Script is up to date.
* 2024-08-09 15:46:46 (803) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-09 15:46:46 (7323) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-09 15:46:46 (7324) [[32mINFO[0m] 
* 2024-08-09 15:46:50 (2029) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-09 15:46:50 (2030) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-09 15:46:50 (7323) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-09 15:46:50 (7324) [[32mINFO[0m] 
* 2024-08-09 15:46:50 (7337) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-09 15:46:50 (7337) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-09 15:46:50 (7337) [[32mINFO[0m]               : epel extras updates
* 2024-08-09 15:46:50 (7337) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-09 15:46:50 (7337) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-09 15:46:50 (7354) [[32mINFO[0m] 
* 2024-08-09 15:46:52 (2039) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-09 15:46:52 (2040) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-09 15:46:52 (1058) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-09 15:46:52 (6442) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/786DvKobeF/ea_profile.json
* 2024-08-09 15:46:56 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/786DvKobeF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-09 15:46:56 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-10 02:12:37 (8642) [[32mINFO[0m] Self-update of script version 51 requested.
* 2024-08-10 02:12:37 (8664) [[32mINFO[0m] Script is up to date.
* 2024-08-10 02:12:39 (803) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-10 02:12:39 (7323) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-10 02:12:39 (7324) [[32mINFO[0m] 
* 2024-08-10 02:12:43 (2029) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-10 02:12:43 (2030) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-10 02:12:43 (7323) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-10 02:12:43 (7324) [[32mINFO[0m] 
* 2024-08-10 02:12:43 (7337) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-10 02:12:43 (7337) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-10 02:12:43 (7337) [[32mINFO[0m]               : epel extras updates
* 2024-08-10 02:12:43 (7337) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-10 02:12:43 (7337) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-10 02:12:43 (7354) [[32mINFO[0m] 
* 2024-08-10 02:12:45 (2039) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-10 02:12:45 (2040) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-10 02:12:45 (1058) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-10 02:12:45 (6442) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/B5jmknk9Rs/ea_profile.json
* 2024-08-10 02:12:48 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/B5jmknk9Rs/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-10 02:12:48 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-11 02:12:41 (8642) [[32mINFO[0m] Self-update of script version 51 requested.
* 2024-08-11 02:12:41 (8664) [[32mINFO[0m] Script is up to date.
* 2024-08-11 02:12:43 (803) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-11 02:12:43 (7323) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-11 02:12:43 (7324) [[32mINFO[0m] 
* 2024-08-11 02:12:49 (2029) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-11 02:12:49 (2030) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-11 02:12:49 (7323) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-11 02:12:49 (7324) [[32mINFO[0m] 
* 2024-08-11 02:12:50 (7337) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-11 02:12:50 (7337) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-11 02:12:50 (7337) [[32mINFO[0m]               : epel extras updates
* 2024-08-11 02:12:50 (7337) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-11 02:12:50 (7337) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-11 02:12:50 (7354) [[32mINFO[0m] 
* 2024-08-11 02:12:52 (2039) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-11 02:12:52 (2040) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-11 02:12:52 (1058) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-11 02:12:52 (6442) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qlRUwKP2Z3/ea_profile.json
* 2024-08-11 02:12:56 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qlRUwKP2Z3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-11 02:12:56 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-12 02:12:07 (8642) [[32mINFO[0m] Self-update of script version 51 requested.
* 2024-08-12 02:12:07 (8664) [[32mINFO[0m] Script is up to date.
* 2024-08-12 02:12:09 (803) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-12 02:12:09 (7323) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-12 02:12:09 (7324) [[32mINFO[0m] 
* 2024-08-12 02:13:12 (2029) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2024-08-12 02:13:12 (2030) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-12 02:13:12 (7323) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-12 02:13:12 (7324) [[32mINFO[0m] 
* 2024-08-12 02:13:12 (7337) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-12 02:13:12 (7337) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-12 02:13:12 (7337) [[32mINFO[0m]               : epel extras updates
* 2024-08-12 02:13:12 (7337) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-12 02:13:12 (7337) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-12 02:13:12 (7354) [[32mINFO[0m] 
* 2024-08-12 02:13:14 (2039) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-12 02:13:14 (2040) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-12 02:13:14 (1058) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-12 02:13:14 (6442) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FkvPuXCdnJ/ea_profile.json
* 2024-08-12 02:13:18 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FkvPuXCdnJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-12 02:13:18 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-13 02:12:09 (8642) [[32mINFO[0m] Self-update of script version 51 requested.
* 2024-08-13 02:12:09 (8664) [[32mINFO[0m] Script is up to date.
* 2024-08-13 02:12:11 (803) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-13 02:12:11 (7323) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-13 02:12:11 (7324) [[32mINFO[0m] 
* 2024-08-13 02:12:15 (2029) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-13 02:12:15 (2030) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-13 02:12:15 (7323) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-13 02:12:15 (7324) [[32mINFO[0m] 
* 2024-08-13 02:12:15 (7337) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-13 02:12:15 (7337) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-13 02:12:15 (7337) [[32mINFO[0m]               : epel extras updates
* 2024-08-13 02:12:15 (7337) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-13 02:12:15 (7337) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-13 02:12:15 (7354) [[32mINFO[0m] 
* 2024-08-13 02:12:16 (2039) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-13 02:12:16 (2040) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-13 02:12:17 (1058) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-13 02:12:17 (6442) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6VU_TE4tLG/ea_profile.json
* 2024-08-13 02:12:20 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6VU_TE4tLG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-13 02:12:20 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-14 02:12:12 (8642) [[32mINFO[0m] Self-update of script version 51 requested.
* 2024-08-14 02:12:14 (8664) [[32mINFO[0m] Script is up to date.
* 2024-08-14 02:12:16 (803) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-14 02:12:16 (7323) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-14 02:12:16 (7324) [[32mINFO[0m] 
* 2024-08-14 02:12:20 (2029) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-14 02:12:20 (2030) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-14 02:12:20 (7323) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-14 02:12:20 (7324) [[32mINFO[0m] 
* 2024-08-14 02:12:20 (7337) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-14 02:12:20 (7337) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-14 02:12:20 (7337) [[32mINFO[0m]               : epel extras updates
* 2024-08-14 02:12:20 (7337) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-14 02:12:20 (7337) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-14 02:12:20 (7354) [[32mINFO[0m] 
* 2024-08-14 02:12:22 (2039) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-14 02:12:22 (2040) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-14 02:12:22 (1058) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-14 02:12:22 (6442) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eU7fCkQf9t/ea_profile.json
* 2024-08-14 02:12:29 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eU7fCkQf9t/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-14 02:12:29 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-15 02:12:13 (8642) [[32mINFO[0m] Self-update of script version 51 requested.
* 2024-08-15 02:12:14 (8664) [[32mINFO[0m] Script is up to date.
* 2024-08-15 02:12:16 (803) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-15 02:12:16 (7323) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-15 02:12:16 (7324) [[32mINFO[0m] 
* 2024-08-15 02:12:22 (2029) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-15 02:12:22 (2030) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-15 02:12:22 (7323) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-15 02:12:22 (7324) [[32mINFO[0m] 
* 2024-08-15 02:12:22 (7337) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-15 02:12:22 (7337) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-15 02:12:22 (7337) [[32mINFO[0m]               : epel extras updates
* 2024-08-15 02:12:22 (7337) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-15 02:12:22 (7337) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-15 02:12:22 (7354) [[32mINFO[0m] 
* 2024-08-15 02:12:24 (2039) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-15 02:12:24 (2040) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-15 02:12:25 (1058) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-15 02:12:25 (6442) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/f1kiOvAGiV/ea_profile.json
* 2024-08-15 02:12:28 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/f1kiOvAGiV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-15 02:12:28 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-16 02:12:10 (8642) [[32mINFO[0m] Self-update of script version 51 requested.
* 2024-08-16 02:12:11 (8664) [[32mINFO[0m] Script is up to date.
* 2024-08-16 02:12:13 (803) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-16 02:12:13 (7323) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-16 02:12:13 (7324) [[32mINFO[0m] 
* 2024-08-16 02:12:19 (2029) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-16 02:12:19 (2030) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-16 02:12:19 (7323) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-16 02:12:19 (7324) [[32mINFO[0m] 
* 2024-08-16 02:12:20 (7337) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-16 02:12:20 (7337) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-16 02:12:20 (7337) [[32mINFO[0m]               : epel extras updates
* 2024-08-16 02:12:20 (7337) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-16 02:12:20 (7337) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-16 02:12:20 (7354) [[32mINFO[0m] 
* 2024-08-16 02:12:22 (2039) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-16 02:12:22 (2040) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-16 02:12:22 (1058) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-16 02:12:22 (6442) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yzXRPLMzRs/ea_profile.json
* 2024-08-16 02:12:26 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yzXRPLMzRs/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-16 02:12:26 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-16 15:46:14 (8642) [[32mINFO[0m] Self-update of script version 51 requested.
* 2024-08-16 15:46:14 (8664) [[32mINFO[0m] Script is up to date.
* 2024-08-16 15:46:16 (803) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-16 15:46:16 (7323) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-16 15:46:16 (7324) [[32mINFO[0m] 
* 2024-08-16 15:46:52 (2029) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-16 15:46:52 (2030) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-16 15:46:52 (7323) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-16 15:46:52 (7324) [[32mINFO[0m] 
* 2024-08-16 15:46:53 (7337) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-16 15:46:53 (7337) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-16 15:46:53 (7337) [[32mINFO[0m]               : epel extras updates
* 2024-08-16 15:46:53 (7337) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-16 15:46:53 (7337) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-16 15:46:53 (7354) [[32mINFO[0m] 
* 2024-08-16 15:47:08 (2039) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-16 15:47:08 (2040) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-16 15:47:09 (1058) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-16 15:47:09 (6442) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DnK0lbqYzc/ea_profile.json
* 2024-08-16 15:47:12 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DnK0lbqYzc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-16 15:47:12 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-17 02:12:45 (8642) [[32mINFO[0m] Self-update of script version 51 requested.
* 2024-08-17 02:12:45 (8664) [[32mINFO[0m] Script is up to date.
* 2024-08-17 02:12:47 (803) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-17 02:12:47 (7323) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-17 02:12:47 (7324) [[32mINFO[0m] 
* 2024-08-17 02:12:52 (2029) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-17 02:12:52 (2030) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-17 02:12:52 (7323) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-17 02:12:52 (7324) [[32mINFO[0m] 
* 2024-08-17 02:12:52 (7337) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-17 02:12:52 (7337) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-17 02:12:52 (7337) [[32mINFO[0m]               : epel extras updates
* 2024-08-17 02:12:52 (7337) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-17 02:12:52 (7337) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-17 02:12:52 (7354) [[32mINFO[0m] 
* 2024-08-17 02:12:54 (2039) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-17 02:12:54 (2040) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-17 02:12:54 (1058) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-17 02:12:54 (6442) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/r7iFCD_n7u/ea_profile.json
* 2024-08-17 02:12:57 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/r7iFCD_n7u/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-17 02:12:57 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-18 02:12:34 (8642) [[32mINFO[0m] Self-update of script version 51 requested.
* 2024-08-18 02:12:34 (8664) [[32mINFO[0m] Script is up to date.
* 2024-08-18 02:12:36 (803) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-18 02:12:36 (7323) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-18 02:12:36 (7324) [[32mINFO[0m] 
* 2024-08-18 02:13:10 (2029) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2024-08-18 02:13:10 (2030) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-18 02:13:10 (7323) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-18 02:13:10 (7324) [[32mINFO[0m] 
* 2024-08-18 02:13:10 (7337) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-18 02:13:10 (7337) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-18 02:13:10 (7337) [[32mINFO[0m]               : epel extras updates
* 2024-08-18 02:13:10 (7337) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-18 02:13:10 (7337) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-18 02:13:10 (7354) [[32mINFO[0m] 
* 2024-08-18 02:13:11 (2039) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-18 02:13:11 (2040) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-18 02:13:11 (1058) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-18 02:13:11 (6442) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XpYzAiydiE/ea_profile.json
* 2024-08-18 02:13:14 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XpYzAiydiE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-18 02:13:14 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-19 02:12:14 (8642) [[32mINFO[0m] Self-update of script version 51 requested.
* 2024-08-19 02:12:15 (8664) [[32mINFO[0m] Script is up to date.
* 2024-08-19 02:12:17 (803) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-19 02:12:17 (7323) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-19 02:12:17 (7324) [[32mINFO[0m] 
* 2024-08-19 02:13:19 (2029) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2024-08-19 02:13:19 (2030) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-19 02:13:19 (7323) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-19 02:13:19 (7324) [[32mINFO[0m] 
* 2024-08-19 02:13:19 (7337) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-19 02:13:19 (7337) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-19 02:13:19 (7337) [[32mINFO[0m]               : epel extras updates
* 2024-08-19 02:13:20 (7337) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-19 02:13:20 (7337) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-19 02:13:20 (7354) [[32mINFO[0m] 
* 2024-08-19 02:13:21 (2039) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-19 02:13:21 (2040) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-19 02:13:21 (1058) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-19 02:13:21 (6442) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AELQsiACAe/ea_profile.json
* 2024-08-19 02:13:26 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AELQsiACAe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-19 02:13:26 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-20 02:12:11 (8642) [[32mINFO[0m] Self-update of script version 51 requested.
* 2024-08-20 02:12:11 (8664) [[32mINFO[0m] Script is up to date.
* 2024-08-20 02:12:13 (803) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-20 02:12:13 (7323) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-20 02:12:13 (7324) [[32mINFO[0m] 
* 2024-08-20 02:12:16 (2029) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-20 02:12:16 (2030) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-20 02:12:16 (7323) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-20 02:12:16 (7324) [[32mINFO[0m] 
* 2024-08-20 02:12:17 (7337) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-20 02:12:17 (7337) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-20 02:12:17 (7337) [[32mINFO[0m]               : epel extras updates
* 2024-08-20 02:12:17 (7337) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-20 02:12:17 (7337) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-20 02:12:17 (7354) [[32mINFO[0m] 
* 2024-08-20 02:12:18 (2039) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-20 02:12:18 (2040) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-20 02:12:18 (1058) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-20 02:12:18 (6442) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XLVxuUuiiV/ea_profile.json
* 2024-08-20 02:12:21 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XLVxuUuiiV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-20 02:12:21 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-21 02:12:07 (8642) [[32mINFO[0m] Self-update of script version 51 requested.
* 2024-08-21 02:12:08 (8664) [[32mINFO[0m] Script is up to date.
* 2024-08-21 02:12:10 (803) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-21 02:12:10 (7323) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-21 02:12:10 (7324) [[32mINFO[0m] 
* 2024-08-21 02:12:16 (2029) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-21 02:12:16 (2030) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-21 02:12:16 (7323) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-21 02:12:16 (7324) [[32mINFO[0m] 
* 2024-08-21 02:12:16 (7337) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-21 02:12:16 (7337) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-21 02:12:16 (7337) [[32mINFO[0m]               : epel extras updates
* 2024-08-21 02:12:16 (7337) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-21 02:12:16 (7337) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-21 02:12:16 (7354) [[32mINFO[0m] 
* 2024-08-21 02:12:19 (2039) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:19 (2040) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-21 02:12:19 (1058) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-21 02:12:19 (6442) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yYQnHwPcaU/ea_profile.json
* 2024-08-21 02:12:24 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yYQnHwPcaU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-21 02:12:24 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-22 02:12:09 (8642) [[32mINFO[0m] Self-update of script version 51 requested.
* 2024-08-22 02:12:15 (8664) [[32mINFO[0m] Script is up to date.
* 2024-08-22 02:12:19 (803) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-22 02:12:19 (7323) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-22 02:12:19 (7324) [[32mINFO[0m] 
* 2024-08-22 02:12:22 (2029) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-22 02:12:22 (2030) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-22 02:12:22 (7323) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-22 02:12:22 (7324) [[32mINFO[0m] 
* 2024-08-22 02:12:22 (7337) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-22 02:12:22 (7337) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-22 02:12:22 (7337) [[32mINFO[0m]               : epel extras updates
* 2024-08-22 02:12:22 (7337) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-22 02:12:22 (7337) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-22 02:12:22 (7354) [[32mINFO[0m] 
* 2024-08-22 02:12:24 (2039) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-22 02:12:24 (2040) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-22 02:12:24 (1058) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-22 02:12:24 (6442) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xBYVX9ubOV/ea_profile.json
* 2024-08-22 02:12:27 (386) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xBYVX9ubOV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-22 02:12:27 (350) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-23 02:12:12 (8642) [[32mINFO[0m] Self-update of script version 51 requested.
* 2024-08-23 02:12:12 (8647) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-08-23 02:12:14 (8656) [[32mINFO[0m] Script update to version 52 successful.
* 2024-08-23 02:12:15 (737) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-23 02:12:15 (7573) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-23 02:12:15 (7574) [[32mINFO[0m] 
* 2024-08-23 02:12:24 (1963) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-23 02:12:24 (1964) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-23 02:12:24 (7573) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-23 02:12:24 (7574) [[32mINFO[0m] 
* 2024-08-23 02:12:24 (7587) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-23 02:12:24 (7587) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-23 02:12:24 (7587) [[32mINFO[0m]               : epel extras updates
* 2024-08-23 02:12:24 (7587) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-23 02:12:24 (7587) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-23 02:12:24 (7604) [[32mINFO[0m] 
* 2024-08-23 02:12:28 (1973) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-23 02:12:28 (1974) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-23 02:12:28 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-23 02:12:28 (6692) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zN3JqhAjnR/ea_profile.json
* 2024-08-23 02:12:34 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zN3JqhAjnR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-23 02:12:34 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-23 15:46:17 (8917) [[32mINFO[0m] Self-update of script version 52 requested.
* 2024-08-23 15:46:18 (8939) [[32mINFO[0m] Script is up to date.
* 2024-08-23 15:46:19 (737) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-23 15:46:19 (7573) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-23 15:46:19 (7574) [[32mINFO[0m] 
* 2024-08-23 15:46:34 (1963) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-23 15:46:34 (1964) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-23 15:46:34 (7573) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-23 15:46:34 (7574) [[32mINFO[0m] 
* 2024-08-23 15:46:34 (7587) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-23 15:46:34 (7587) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-23 15:46:34 (7587) [[32mINFO[0m]               : epel extras updates
* 2024-08-23 15:46:34 (7587) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-23 15:46:34 (7587) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-23 15:46:34 (7604) [[32mINFO[0m] 
* 2024-08-23 15:46:38 (1973) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-23 15:46:38 (1974) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-23 15:46:38 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-23 15:46:38 (6692) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/v7D_ABobK9/ea_profile.json
* 2024-08-23 15:46:45 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/v7D_ABobK9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-23 15:46:45 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-24 02:12:37 (8917) [[32mINFO[0m] Self-update of script version 52 requested.
* 2024-08-24 02:12:38 (8939) [[32mINFO[0m] Script is up to date.
* 2024-08-24 02:12:39 (737) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-24 02:12:39 (7573) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-24 02:12:39 (7574) [[32mINFO[0m] 
* 2024-08-24 02:12:44 (1963) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-24 02:12:44 (1964) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-24 02:12:44 (7573) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-24 02:12:44 (7574) [[32mINFO[0m] 
* 2024-08-24 02:12:44 (7587) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-24 02:12:44 (7587) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-24 02:12:44 (7587) [[32mINFO[0m]               : epel extras updates
* 2024-08-24 02:12:44 (7587) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-24 02:12:44 (7587) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-24 02:12:44 (7604) [[32mINFO[0m] 
* 2024-08-24 02:12:45 (1973) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-24 02:12:45 (1974) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-24 02:12:45 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-24 02:12:45 (6692) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/N6Cnp7pu6o/ea_profile.json
* 2024-08-24 02:12:48 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/N6Cnp7pu6o/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-24 02:12:48 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-25 02:12:35 (8917) [[32mINFO[0m] Self-update of script version 52 requested.
* 2024-08-25 02:12:36 (8939) [[32mINFO[0m] Script is up to date.
* 2024-08-25 02:12:37 (737) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-25 02:12:37 (7573) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-25 02:12:37 (7574) [[32mINFO[0m] 
* 2024-08-25 02:12:44 (1963) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-25 02:12:44 (1964) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-25 02:12:44 (7573) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-25 02:12:44 (7574) [[32mINFO[0m] 
* 2024-08-25 02:12:44 (7587) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-25 02:12:44 (7587) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-25 02:12:44 (7587) [[32mINFO[0m]               : epel extras updates
* 2024-08-25 02:12:44 (7587) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-25 02:12:44 (7587) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-25 02:12:44 (7604) [[32mINFO[0m] 
* 2024-08-25 02:12:47 (1973) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:47 (1974) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-25 02:12:47 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-25 02:12:47 (6692) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JTw9xrC_Rt/ea_profile.json
* 2024-08-25 02:12:52 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JTw9xrC_Rt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-25 02:12:52 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-26 02:12:15 (8917) [[32mINFO[0m] Self-update of script version 52 requested.
* 2024-08-26 02:12:16 (8939) [[32mINFO[0m] Script is up to date.
* 2024-08-26 02:12:17 (737) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-26 02:12:17 (7573) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-26 02:12:17 (7574) [[32mINFO[0m] 
* 2024-08-26 02:12:23 (1963) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-26 02:12:23 (1964) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-26 02:12:23 (7573) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-26 02:12:23 (7574) [[32mINFO[0m] 
* 2024-08-26 02:12:23 (7587) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-26 02:12:23 (7587) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-26 02:12:23 (7587) [[32mINFO[0m]               : epel extras updates
* 2024-08-26 02:12:23 (7587) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-26 02:12:23 (7587) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-26 02:12:23 (7604) [[32mINFO[0m] 
* 2024-08-26 02:12:25 (1973) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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 02:12:25 (1974) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-26 02:12:25 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-26 02:12:25 (6692) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MdNeiQvBTa/ea_profile.json
* 2024-08-26 02:12:28 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MdNeiQvBTa/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-26 02:12:28 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-27 02:12:08 (8917) [[32mINFO[0m] Self-update of script version 52 requested.
* 2024-08-27 02:12:09 (8939) [[32mINFO[0m] Script is up to date.
* 2024-08-27 02:12:10 (737) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-27 02:12:10 (7573) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-27 02:12:10 (7574) [[32mINFO[0m] 
* 2024-08-27 02:12:16 (1963) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-27 02:12:16 (1964) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-27 02:12:16 (7573) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-27 02:12:16 (7574) [[32mINFO[0m] 
* 2024-08-27 02:12:16 (7587) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-27 02:12:16 (7587) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-27 02:12:16 (7587) [[32mINFO[0m]               : epel extras updates
* 2024-08-27 02:12:16 (7587) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-27 02:12:16 (7587) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-27 02:12:16 (7604) [[32mINFO[0m] 
* 2024-08-27 02:12:19 (1973) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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 02:12:19 (1974) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-27 02:12:19 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-27 02:12:19 (6692) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lXh5T6RvLH/ea_profile.json
* 2024-08-27 02:12:23 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lXh5T6RvLH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-27 02:12:23 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-28 02:14:15 (8917) [[32mINFO[0m] Self-update of script version 52 requested.
* 2024-08-28 02:14:15 (8939) [[32mINFO[0m] Script is up to date.
* 2024-08-28 02:14:17 (737) [[33mWARN[0m] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.
* 2024-08-28 02:14:17 (7573) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-08-28 02:14:17 (7574) [[32mINFO[0m] 
* 2024-08-28 02:14:23 (1963) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-28 02:14:23 (1964) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-08-28 02:14:23 (7573) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-08-28 02:14:23 (7574) [[32mINFO[0m] 
* 2024-08-28 02:14:24 (7587) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-28 02:14:24 (7587) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-08-28 02:14:24 (7587) [[32mINFO[0m]               : epel extras updates
* 2024-08-28 02:14:24 (7587) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-08-28 02:14:24 (7587) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-08-28 02:14:24 (7604) [[32mINFO[0m] 
* 2024-08-28 02:14:26 (1973) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-28 02:14:26 (1974) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-08-28 02:14:26 (992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-28 02:14:26 (6692) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zjmT4FXtDx/ea_profile.json
* 2024-08-28 02:14:30 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zjmT4FXtDx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-28 02:14:30 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-29 02:12:06 (8917) [[32mINFO[0m] Self-update of script version 52 requested.
* 2024-08-29 02:12:06 (8939) [[32mINFO[0m] Script is up to date.
* 2024-08-29 02:12:08 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: Signature verification failed for URL 'http://repo-ir.amazeservice.net/cpanelsync/TIERS.json'. Signature rollback detected. Please see https://go.cpanel.net/sigerrors for further information about this error.
* 2024-08-29 02:12:08 (390) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 2369.
* 2024-08-29 02:12:08 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-30 02:12:05 (8917) [[32mINFO[0m] Self-update of script version 52 requested.
* 2024-08-30 02:12:07 (8922) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-08-30 02:12:08 (8931) [[32mINFO[0m] Script update to version 53 successful.
* 2024-08-30 02:12:10 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: Signature verification failed for URL 'http://repo-ir.amazeservice.net/cpanelsync/TIERS.json'. Signature rollback detected. Please see https://go.cpanel.net/sigerrors for further information about this error.
* 2024-08-30 02:12:10 (391) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 2372.
* 2024-08-30 02:12:10 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-30 15:46:06 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-08-30 15:46:07 (9014) [[32mINFO[0m] Script is up to date.
* 2024-08-30 15:46:09 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: Signature verification failed for URL 'http://repo-ir.amazeservice.net/cpanelsync/TIERS.json'. Signature rollback detected. Please see https://go.cpanel.net/sigerrors for further information about this error.
* 2024-08-30 15:46:09 (391) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 2372.
* 2024-08-30 15:46:09 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-31 02:13:01 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-08-31 02:13:01 (9014) [[32mINFO[0m] Script is up to date.
* 2024-08-31 02:13:03 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: Signature verification failed for URL 'http://repo-ir.amazeservice.net/cpanelsync/TIERS.json'. Signature rollback detected. Please see https://go.cpanel.net/sigerrors for further information about this error.
* 2024-08-31 02:13:03 (391) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 2372.
* 2024-08-31 02:13:03 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-01 02:12:29 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-01 02:12:30 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-01 02:12:31 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: Signature verification failed for URL 'http://repo-ir.amazeservice.net/cpanelsync/TIERS.json'. Signature rollback detected. Please see https://go.cpanel.net/sigerrors for further information about this error.
* 2024-09-01 02:12:31 (391) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 2372.
* 2024-09-01 02:12:31 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-02 02:12:06 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-02 02:12:07 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-02 02:12:08 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: Signature verification failed for URL 'http://repo-ir.amazeservice.net/cpanelsync/TIERS.json'. Signature rollback detected. Please see https://go.cpanel.net/sigerrors for further information about this error.
* 2024-09-02 02:12:08 (391) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 2372.
* 2024-09-02 02:12:08 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-03 02:12:05 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-03 02:12:06 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-03 02:12:07 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: Signature verification failed for URL 'http://repo-ir.amazeservice.net/cpanelsync/TIERS.json'. Signature rollback detected. Please see https://go.cpanel.net/sigerrors for further information about this error.
* 2024-09-03 02:12:07 (391) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 2372.
* 2024-09-03 02:12:07 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-04 02:12:06 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-04 02:12:06 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-04 02:12:08 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-04 02:12:08 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-04 02:12:08 (7647) [[32mINFO[0m] 
* 2024-09-04 02:12:11 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-04 02:12:11 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-04 02:12:11 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-04 02:12:11 (7647) [[32mINFO[0m] 
* 2024-09-04 02:12:11 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-04 02:12:11 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-04 02:12:11 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-04 02:12:11 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-04 02:12:11 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-04 02:12:11 (7677) [[32mINFO[0m] 
* 2024-09-04 02:12:12 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:12 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-04 02:12:13 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-04 02:12:13 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_dIjLBwPYE/ea_profile.json
* 2024-09-04 02:12:15 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_dIjLBwPYE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-04 02:12:15 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-05 02:12:06 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-05 02:12:07 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-05 02:12:08 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-05 02:12:08 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-05 02:12:08 (7647) [[32mINFO[0m] 
* 2024-09-05 02:12:44 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2024-09-05 02:12:44 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-05 02:12:44 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-05 02:12:44 (7647) [[32mINFO[0m] 
* 2024-09-05 02:12:44 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-05 02:12:44 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-05 02:12:44 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-05 02:12:44 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-05 02:12:44 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-05 02:12:44 (7677) [[32mINFO[0m] 
* 2024-09-05 02:13:16 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:13:16 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2024-09-05 02:13:16 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-05 02:13:16 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Or5Hv984BC/ea_profile.json
* 2024-09-05 02:13:20 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Or5Hv984BC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-05 02:13:20 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-06 02:12:07 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-06 02:12:07 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-06 02:12:09 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-06 02:12:09 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-06 02:12:09 (7647) [[32mINFO[0m] 
* 2024-09-06 02:12:13 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-06 02:12:13 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-06 02:12:13 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-06 02:12:13 (7647) [[32mINFO[0m] 
* 2024-09-06 02:12:14 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-06 02:12:14 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-06 02:12:14 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-06 02:12:14 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-06 02:12:14 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-06 02:12:14 (7677) [[32mINFO[0m] 
* 2024-09-06 02:12:15 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-06 02:12:15 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-06 02:12:15 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-06 02:12:15 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qTX2LrJDH4/ea_profile.json
* 2024-09-06 02:12:19 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qTX2LrJDH4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-06 02:12:19 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-06 15:46:09 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-06 15:46:10 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-06 15:46:11 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-06 15:46:11 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-06 15:46:11 (7647) [[32mINFO[0m] 
* 2024-09-06 15:46:16 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-06 15:46:16 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-06 15:46:16 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-06 15:46:16 (7647) [[32mINFO[0m] 
* 2024-09-06 15:46:16 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-06 15:46:16 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-06 15:46:16 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-06 15:46:16 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-06 15:46:16 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-06 15:46:16 (7677) [[32mINFO[0m] 
* 2024-09-06 15:46:38 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-06 15:46:38 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-06 15:46:39 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-06 15:46:39 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ftWC2_Kwl3/ea_profile.json
* 2024-09-06 15:46:43 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ftWC2_Kwl3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-06 15:46:43 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-07 02:12:36 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-07 02:12:37 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-07 02:12:57 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-07 02:12:57 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-07 02:12:57 (7647) [[32mINFO[0m] 
* 2024-09-07 02:13:01 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-07 02:13:01 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-07 02:13:01 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-07 02:13:01 (7647) [[32mINFO[0m] 
* 2024-09-07 02:13:01 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-07 02:13:01 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-07 02:13:01 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-07 02:13:01 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-07 02:13:01 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-07 02:13:01 (7677) [[32mINFO[0m] 
* 2024-09-07 02:13:03 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-07 02:13:03 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-07 02:13:03 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-07 02:13:03 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dxEAqiwfyH/ea_profile.json
* 2024-09-07 02:13:06 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dxEAqiwfyH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-07 02:13:06 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-08 02:12:34 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-08 02:12:34 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-08 02:12:36 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-08 02:12:36 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-08 02:12:36 (7647) [[32mINFO[0m] 
* 2024-09-08 02:12:40 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-08 02:12:40 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-08 02:12:40 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-08 02:12:40 (7647) [[32mINFO[0m] 
* 2024-09-08 02:12:40 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-08 02:12:40 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-08 02:12:40 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-08 02:12:40 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-08 02:12:40 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-08 02:12:40 (7677) [[32mINFO[0m] 
* 2024-09-08 02:12:41 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-08 02:12:41 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-08 02:12:42 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-08 02:12:42 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xOmHZ3SVpf/ea_profile.json
* 2024-09-08 02:12:45 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xOmHZ3SVpf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-08 02:12:45 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-09 02:12:06 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-09 02:12:06 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-09 02:12:08 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-09 02:12:08 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-09 02:12:08 (7647) [[32mINFO[0m] 
* 2024-09-09 02:12:12 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-09 02:12:12 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-09 02:12:12 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-09 02:12:12 (7647) [[32mINFO[0m] 
* 2024-09-09 02:12:12 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-09 02:12:12 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-09 02:12:12 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-09 02:12:12 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-09 02:12:12 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-09 02:12:12 (7677) [[32mINFO[0m] 
* 2024-09-09 02:12:14 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-09 02:12:14 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-09 02:12:14 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-09 02:12:14 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WopCmsTf3t/ea_profile.json
* 2024-09-09 02:12:17 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WopCmsTf3t/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-09 02:12:17 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-10 02:12:11 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-10 02:12:11 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-10 02:12:13 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-10 02:12:13 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-10 02:12:13 (7647) [[32mINFO[0m] 
* 2024-09-10 02:12:17 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-10 02:12:17 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-10 02:12:17 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-10 02:12:17 (7647) [[32mINFO[0m] 
* 2024-09-10 02:12:18 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-10 02:12:18 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-10 02:12:18 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-10 02:12:18 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-10 02:12:18 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-10 02:12:18 (7677) [[32mINFO[0m] 
* 2024-09-10 02:12:20 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-10 02:12:20 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-10 02:12:20 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-10 02:12:20 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/c0CsAbYD__/ea_profile.json
* 2024-09-10 02:12:24 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/c0CsAbYD__/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-10 02:12:24 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-11 02:12:09 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-11 02:12:10 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-11 02:12:11 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-11 02:12:11 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-11 02:12:11 (7647) [[32mINFO[0m] 
* 2024-09-11 02:12:16 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-11 02:12:16 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-11 02:12:16 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-11 02:12:16 (7647) [[32mINFO[0m] 
* 2024-09-11 02:12:16 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-11 02:12:16 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-11 02:12:16 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-11 02:12:16 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-11 02:12:16 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-11 02:12:16 (7677) [[32mINFO[0m] 
* 2024-09-11 02:12:18 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-11 02:12:18 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-11 02:12:18 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-11 02:12:18 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2Yl1ylrk2_/ea_profile.json
* 2024-09-11 02:12:21 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2Yl1ylrk2_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-11 02:12:21 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-12 02:12:08 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-12 02:12:08 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-12 02:12:10 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-12 02:12:10 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-12 02:12:10 (7647) [[32mINFO[0m] 
* 2024-09-12 02:12:13 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-12 02:12:13 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-12 02:12:13 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-12 02:12:13 (7647) [[32mINFO[0m] 
* 2024-09-12 02:12:13 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-12 02:12:13 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-12 02:12:13 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-12 02:12:13 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-12 02:12:13 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-12 02:12:13 (7677) [[32mINFO[0m] 
* 2024-09-12 02:12:14 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-12 02:12:14 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-12 02:12:14 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-12 02:12:14 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GqetVroPva/ea_profile.json
* 2024-09-12 02:12:17 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GqetVroPva/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-12 02:12:17 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-13 02:12:07 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-13 02:12:07 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-13 02:12:09 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-13 02:12:09 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-13 02:12:09 (7647) [[32mINFO[0m] 
* 2024-09-13 02:12:13 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-13 02:12:13 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-13 02:12:13 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-13 02:12:13 (7647) [[32mINFO[0m] 
* 2024-09-13 02:12:13 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-13 02:12:13 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-13 02:12:13 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-13 02:12:13 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-13 02:12:13 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-13 02:12:13 (7677) [[32mINFO[0m] 
* 2024-09-13 02:12:14 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-13 02:12:14 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-13 02:12:15 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-13 02:12:15 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4kbe8xruti/ea_profile.json
* 2024-09-13 02:12:17 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4kbe8xruti/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-13 02:12:17 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-13 15:46:41 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-13 15:46:41 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-13 15:46:43 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-13 15:46:43 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-13 15:46:43 (7647) [[32mINFO[0m] 
* 2024-09-13 15:46:48 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-13 15:46:48 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-13 15:46:48 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-13 15:46:48 (7647) [[32mINFO[0m] 
* 2024-09-13 15:46:48 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-13 15:46:49 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-13 15:46:49 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-13 15:46:49 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-13 15:46:49 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-13 15:46:49 (7677) [[32mINFO[0m] 
* 2024-09-13 15:46:50 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-13 15:46:50 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-13 15:46:51 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-13 15:46:51 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9NBYEjsJWW/ea_profile.json
* 2024-09-13 15:46:54 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9NBYEjsJWW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-13 15:46:54 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-14 02:12:32 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-14 02:12:32 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-14 02:12:34 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-14 02:12:34 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-14 02:12:34 (7647) [[32mINFO[0m] 
* 2024-09-14 02:12:37 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-14 02:12:37 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-14 02:12:37 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-14 02:12:37 (7647) [[32mINFO[0m] 
* 2024-09-14 02:12:37 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-14 02:12:37 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-14 02:12:37 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-14 02:12:37 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-14 02:12:37 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-14 02:12:37 (7677) [[32mINFO[0m] 
* 2024-09-14 02:12:37 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-14 02:12:37 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-14 02:12:38 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-14 02:12:38 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1yjqAUPpRG/ea_profile.json
* 2024-09-14 02:12:40 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1yjqAUPpRG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-14 02:12:40 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-15 02:12:35 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-15 02:12:35 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-15 02:12:37 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-15 02:12:37 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-15 02:12:37 (7647) [[32mINFO[0m] 
* 2024-09-15 02:12:40 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-15 02:12:40 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-15 02:12:40 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-15 02:12:40 (7647) [[32mINFO[0m] 
* 2024-09-15 02:12:40 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-15 02:12:40 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-15 02:12:40 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-15 02:12:40 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-15 02:12:40 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-15 02:12:40 (7677) [[32mINFO[0m] 
* 2024-09-15 02:12:41 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:41 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-15 02:12:41 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-15 02:12:41 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YlKl2MjYeA/ea_profile.json
* 2024-09-15 02:12:44 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YlKl2MjYeA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-15 02:12:44 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-16 02:12:11 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-16 02:12:11 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-16 02:12:13 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-16 02:12:13 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-16 02:12:13 (7647) [[32mINFO[0m] 
* 2024-09-16 02:12:18 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-16 02:12:18 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-16 02:12:18 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-16 02:12:18 (7647) [[32mINFO[0m] 
* 2024-09-16 02:12:18 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-16 02:12:18 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-16 02:12:18 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-16 02:12:18 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-16 02:12:18 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-16 02:12:18 (7677) [[32mINFO[0m] 
* 2024-09-16 02:12:20 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-16 02:12:20 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-16 02:12:20 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-16 02:12:20 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rfojFvL2Lt/ea_profile.json
* 2024-09-16 02:12:23 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rfojFvL2Lt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-16 02:12:23 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-17 02:12:38 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-17 02:12:38 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-17 02:12:40 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-17 02:12:40 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-17 02:12:40 (7647) [[32mINFO[0m] 
* 2024-09-17 02:12:44 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-17 02:12:44 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-17 02:12:44 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-17 02:12:44 (7647) [[32mINFO[0m] 
* 2024-09-17 02:12:44 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-17 02:12:44 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-17 02:12:44 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-17 02:12:44 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-17 02:12:44 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-17 02:12:44 (7677) [[32mINFO[0m] 
* 2024-09-17 02:12:45 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:45 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-17 02:12:45 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-17 02:12:45 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4KyjE2og94/ea_profile.json
* 2024-09-17 02:12:49 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4KyjE2og94/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-17 02:12:49 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-18 02:12:04 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-18 02:12:04 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-18 02:12:05 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: Signature verification failed for URL 'http://repo-ir.amazeservice.net/cpanelsync/TIERS.json'. Signature rollback detected. Please see https://go.cpanel.net/sigerrors for further information about this error.
* 2024-09-18 02:12:05 (391) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 2372.
* 2024-09-18 02:12:05 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-19 02:12:12 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-19 02:12:12 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-19 02:12:13 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-19 02:12:13 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-19 02:12:13 (7647) [[32mINFO[0m] 
* 2024-09-19 02:12:47 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2024-09-19 02:12:47 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-19 02:12:47 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-19 02:12:47 (7647) [[32mINFO[0m] 
* 2024-09-19 02:12:47 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-19 02:12:47 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-19 02:12:47 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-19 02:12:47 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-19 02:12:47 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-19 02:12:47 (7677) [[32mINFO[0m] 
* 2024-09-19 02:13:18 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:13:18 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2024-09-19 02:13:18 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-19 02:13:18 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OGcwT_Hnju/ea_profile.json
* 2024-09-19 02:13:22 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OGcwT_Hnju/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-19 02:13:22 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-20 02:13:11 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-20 02:13:12 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-20 02:13:13 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-20 02:13:13 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-20 02:13:13 (7647) [[32mINFO[0m] 
* 2024-09-20 02:13:18 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-20 02:13:18 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-20 02:13:18 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-20 02:13:18 (7647) [[32mINFO[0m] 
* 2024-09-20 02:13:18 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-20 02:13:18 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-20 02:13:18 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-20 02:13:18 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-20 02:13:18 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-20 02:13:18 (7677) [[32mINFO[0m] 
* 2024-09-20 02:13:19 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-20 02:13:19 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-20 02:13:19 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-20 02:13:19 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2s0zwVt65E/ea_profile.json
* 2024-09-20 02:13:23 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2s0zwVt65E/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-20 02:13:23 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-20 15:46:10 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-20 15:46:10 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-20 15:46:12 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-20 15:46:12 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-20 15:46:12 (7647) [[32mINFO[0m] 
* 2024-09-20 15:46:20 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-20 15:46:20 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-20 15:46:20 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-20 15:46:20 (7647) [[32mINFO[0m] 
* 2024-09-20 15:46:21 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-20 15:46:21 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-20 15:46:21 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-20 15:46:21 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-20 15:46:21 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-20 15:46:21 (7677) [[32mINFO[0m] 
* 2024-09-20 15:46:24 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-20 15:46:24 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-20 15:46:25 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-20 15:46:25 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BkwOmoLJwU/ea_profile.json
* 2024-09-20 15:46:30 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BkwOmoLJwU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-20 15:46:30 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-21 02:12:38 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-21 02:12:38 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-21 02:12:40 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-21 02:12:40 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-21 02:12:40 (7647) [[32mINFO[0m] 
* 2024-09-21 02:13:14 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-21 02:13:14 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-21 02:13:14 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-21 02:13:14 (7647) [[32mINFO[0m] 
* 2024-09-21 02:13:14 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-21 02:13:14 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-21 02:13:14 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-21 02:13:14 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-21 02:13:14 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-21 02:13:14 (7677) [[32mINFO[0m] 
* 2024-09-21 02:13:45 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-21 02:13:45 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2024-09-21 02:13:45 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-21 02:13:45 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Luooe1QZ0_/ea_profile.json
* 2024-09-21 02:14:16 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Luooe1QZ0_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-21 02:14:16 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-22 02:12:34 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-22 02:12:35 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-22 02:12:36 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-22 02:12:36 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-22 02:12:36 (7647) [[32mINFO[0m] 
* 2024-09-22 02:12:47 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-22 02:12:47 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-22 02:12:47 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-22 02:12:47 (7647) [[32mINFO[0m] 
* 2024-09-22 02:12:47 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-22 02:12:47 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-22 02:12:47 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-22 02:12:47 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-22 02:12:47 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-22 02:12:47 (7677) [[32mINFO[0m] 
* 2024-09-22 02:12:53 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-22 02:12:53 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-22 02:12:53 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-22 02:12:53 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dZedURzwaE/ea_profile.json
* 2024-09-22 02:13:02 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dZedURzwaE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-22 02:13:02 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-23 02:12:15 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-23 02:12:15 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-23 02:12:17 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-23 02:12:17 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-23 02:12:17 (7647) [[32mINFO[0m] 
* 2024-09-23 02:12:20 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-23 02:12:20 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-23 02:12:20 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-23 02:12:20 (7647) [[32mINFO[0m] 
* 2024-09-23 02:12:20 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-23 02:12:20 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-23 02:12:20 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-23 02:12:20 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-23 02:12:20 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-23 02:12:20 (7677) [[32mINFO[0m] 
* 2024-09-23 02:12:21 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-23 02:12:21 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-23 02:12:21 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-23 02:12:21 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VwdScoMux7/ea_profile.json
* 2024-09-23 02:12:24 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VwdScoMux7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-23 02:12:24 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-24 02:12:12 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-24 02:12:13 (9014) [[32mINFO[0m] Script is up to date.
* 2024-09-24 02:12:14 (740) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-24 02:12:14 (7646) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-24 02:12:14 (7647) [[32mINFO[0m] 
* 2024-09-24 02:12:23 (1966) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-24 02:12:23 (1967) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-24 02:12:23 (7646) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-24 02:12:23 (7647) [[32mINFO[0m] 
* 2024-09-24 02:12:23 (7660) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-24 02:12:23 (7660) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-24 02:12:23 (7660) [[32mINFO[0m]               : epel extras updates
* 2024-09-24 02:12:23 (7660) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-24 02:12:23 (7660) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-24 02:12:23 (7677) [[32mINFO[0m] 
* 2024-09-24 02:12:27 (1976) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-24 02:12:27 (1977) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-24 02:12:27 (995) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-24 02:12:27 (6765) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IowFaIn3Eh/ea_profile.json
* 2024-09-24 02:12:32 (391) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IowFaIn3Eh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-24 02:12:32 (355) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-25 02:14:49 (8992) [[32mINFO[0m] Self-update of script version 53 requested.
* 2024-09-25 02:14:49 (8997) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-09-25 02:14:50 (9006) [[32mINFO[0m] Script update to version 54 successful.
* 2024-09-25 02:14:51 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-25 02:14:51 (7666) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-25 02:14:51 (7667) [[32mINFO[0m] 
* 2024-09-25 02:14:56 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-25 02:14:56 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-25 02:14:56 (7666) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-25 02:14:56 (7667) [[32mINFO[0m] 
* 2024-09-25 02:14:56 (7680) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-25 02:14:56 (7680) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-25 02:14:56 (7680) [[32mINFO[0m]               : epel extras updates
* 2024-09-25 02:14:56 (7680) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-25 02:14:56 (7680) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-25 02:14:56 (7697) [[32mINFO[0m] 
* 2024-09-25 02:14:58 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-25 02:14:58 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-25 02:14:58 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-25 02:14:58 (6802) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/F8E8x9JNk8/ea_profile.json
* 2024-09-25 02:15:01 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/F8E8x9JNk8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-25 02:15:01 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-26 02:12:16 (9008) [[32mINFO[0m] Self-update of script version 54 requested.
* 2024-09-26 02:12:16 (9030) [[32mINFO[0m] Script is up to date.
* 2024-09-26 02:12:18 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-26 02:12:18 (7666) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-26 02:12:18 (7667) [[32mINFO[0m] 
* 2024-09-26 02:12:22 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-26 02:12:22 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-26 02:12:22 (7666) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-26 02:12:22 (7667) [[32mINFO[0m] 
* 2024-09-26 02:12:22 (7680) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-26 02:12:22 (7680) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-26 02:12:22 (7680) [[32mINFO[0m]               : epel extras updates
* 2024-09-26 02:12:22 (7680) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-26 02:12:22 (7680) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-26 02:12:22 (7697) [[32mINFO[0m] 
* 2024-09-26 02:12:24 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-26 02:12:24 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-26 02:12:24 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-26 02:12:24 (6802) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vJhRDn3ueQ/ea_profile.json
* 2024-09-26 02:12:28 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vJhRDn3ueQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-26 02:12:28 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-27 02:12:08 (9008) [[32mINFO[0m] Self-update of script version 54 requested.
* 2024-09-27 02:12:08 (9030) [[32mINFO[0m] Script is up to date.
* 2024-09-27 02:12:10 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-27 02:12:10 (7666) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-27 02:12:10 (7667) [[32mINFO[0m] 
* 2024-09-27 02:12:14 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-27 02:12:14 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-27 02:12:14 (7666) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-27 02:12:14 (7667) [[32mINFO[0m] 
* 2024-09-27 02:12:14 (7680) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-27 02:12:14 (7680) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-27 02:12:14 (7680) [[32mINFO[0m]               : epel extras updates
* 2024-09-27 02:12:14 (7680) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-27 02:12:14 (7680) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-27 02:12:14 (7697) [[32mINFO[0m] 
* 2024-09-27 02:12:15 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-27 02:12:15 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-27 02:12:15 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-27 02:12:15 (6802) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9Tw7ybZI1a/ea_profile.json
* 2024-09-27 02:12:19 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9Tw7ybZI1a/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-27 02:12:19 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-27 15:46:09 (9008) [[32mINFO[0m] Self-update of script version 54 requested.
* 2024-09-27 15:46:10 (9030) [[32mINFO[0m] Script is up to date.
* 2024-09-27 15:46:11 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-27 15:46:11 (7666) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-27 15:46:11 (7667) [[32mINFO[0m] 
* 2024-09-27 15:46:44 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-27 15:46:44 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-27 15:46:44 (7666) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-27 15:46:44 (7667) [[32mINFO[0m] 
* 2024-09-27 15:46:44 (7680) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-27 15:46:45 (7680) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-27 15:46:45 (7680) [[32mINFO[0m]               : epel extras updates
* 2024-09-27 15:46:45 (7680) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-27 15:46:45 (7680) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-27 15:46:45 (7697) [[32mINFO[0m] 
* 2024-09-27 15:47:08 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-27 15:47:08 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-27 15:47:09 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-27 15:47:09 (6802) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UXQTGonUWI/ea_profile.json
* 2024-09-27 15:47:25 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UXQTGonUWI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-27 15:47:25 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-28 02:12:44 (9008) [[32mINFO[0m] Self-update of script version 54 requested.
* 2024-09-28 02:12:44 (9030) [[32mINFO[0m] Script is up to date.
* 2024-09-28 02:12:46 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-28 02:12:46 (7666) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-28 02:12:46 (7667) [[32mINFO[0m] 
* 2024-09-28 02:12:50 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-28 02:12:50 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-28 02:12:50 (7666) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-28 02:12:50 (7667) [[32mINFO[0m] 
* 2024-09-28 02:12:50 (7680) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-28 02:12:50 (7680) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-28 02:12:50 (7680) [[32mINFO[0m]               : epel extras updates
* 2024-09-28 02:12:50 (7680) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-28 02:12:50 (7680) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-28 02:12:50 (7697) [[32mINFO[0m] 
* 2024-09-28 02:12:51 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-28 02:12:51 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-28 02:12:52 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-28 02:12:52 (6802) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9f8nNAPbwK/ea_profile.json
* 2024-09-28 02:12:57 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9f8nNAPbwK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-28 02:12:57 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-29 02:12:40 (9008) [[32mINFO[0m] Self-update of script version 54 requested.
* 2024-09-29 02:12:41 (9030) [[32mINFO[0m] Script is up to date.
* 2024-09-29 02:12:42 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-29 02:12:42 (7666) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-29 02:12:42 (7667) [[32mINFO[0m] 
* 2024-09-29 02:12:45 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-29 02:12:45 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-29 02:12:45 (7666) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-29 02:12:45 (7667) [[32mINFO[0m] 
* 2024-09-29 02:12:46 (7680) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-29 02:12:46 (7680) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-29 02:12:46 (7680) [[32mINFO[0m]               : epel extras updates
* 2024-09-29 02:12:46 (7680) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-29 02:12:46 (7680) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-29 02:12:46 (7697) [[32mINFO[0m] 
* 2024-09-29 02:12:46 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-29 02:12:46 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-29 02:12:47 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-29 02:12:47 (6802) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oT61hxiLIT/ea_profile.json
* 2024-09-29 02:12:52 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oT61hxiLIT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-29 02:12:52 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-30 02:12:07 (9008) [[32mINFO[0m] Self-update of script version 54 requested.
* 2024-09-30 02:12:08 (9030) [[32mINFO[0m] Script is up to date.
* 2024-09-30 02:12:09 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-09-30 02:12:09 (7666) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-09-30 02:12:09 (7667) [[32mINFO[0m] 
* 2024-09-30 02:12:12 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-30 02:12:12 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-09-30 02:12:12 (7666) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-09-30 02:12:12 (7667) [[32mINFO[0m] 
* 2024-09-30 02:12:12 (7680) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-30 02:12:12 (7680) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-09-30 02:12:12 (7680) [[32mINFO[0m]               : epel extras updates
* 2024-09-30 02:12:12 (7680) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-09-30 02:12:12 (7680) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-09-30 02:12:12 (7697) [[32mINFO[0m] 
* 2024-09-30 02:12:13 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-30 02:12:13 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-09-30 02:12:13 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-30 02:12:13 (6802) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0QhQUXUSgH/ea_profile.json
* 2024-09-30 02:12:16 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0QhQUXUSgH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-30 02:12:16 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-01 02:12:25 (9008) [[32mINFO[0m] Self-update of script version 54 requested.
* 2024-10-01 02:12:25 (9013) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-10-01 02:12:26 (9022) [[32mINFO[0m] Script update to version 55 successful.
* 2024-10-01 02:12:28 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-01 02:12:28 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-01 02:12:28 (7668) [[32mINFO[0m] 
* 2024-10-01 02:12:32 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-01 02:12:32 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-01 02:12:32 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-01 02:12:32 (7668) [[32mINFO[0m] 
* 2024-10-01 02:12:32 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-01 02:12:32 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-01 02:12:32 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-01 02:12:32 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-01 02:12:32 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-01 02:12:32 (7698) [[32mINFO[0m] 
* 2024-10-01 02:12:33 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-01 02:12:33 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-01 02:12:33 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-01 02:12:33 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iyFuEac1Cm/ea_profile.json
* 2024-10-01 02:12:36 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iyFuEac1Cm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-01 02:12:36 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-02 02:13:23 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-02 02:13:23 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-02 02:13:25 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-02 02:13:25 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-02 02:13:25 (7668) [[32mINFO[0m] 
* 2024-10-02 02:13:29 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-02 02:13:29 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-02 02:13:29 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-02 02:13:29 (7668) [[32mINFO[0m] 
* 2024-10-02 02:13:29 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-02 02:13:29 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-02 02:13:29 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-02 02:13:29 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-02 02:13:29 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-02 02:13:29 (7698) [[32mINFO[0m] 
* 2024-10-02 02:13:30 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-02 02:13:30 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-02 02:13:30 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-02 02:13:30 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FxzUtPV5rp/ea_profile.json
* 2024-10-02 02:13:33 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FxzUtPV5rp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-02 02:13:33 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-03 02:12:16 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-03 02:12:16 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-03 02:12:18 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-03 02:12:18 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-03 02:12:18 (7668) [[32mINFO[0m] 
* 2024-10-03 02:12:25 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-03 02:12:25 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-03 02:12:25 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-03 02:12:25 (7668) [[32mINFO[0m] 
* 2024-10-03 02:12:25 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-03 02:12:26 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-03 02:12:26 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-03 02:12:26 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-03 02:12:26 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-03 02:12:26 (7698) [[32mINFO[0m] 
* 2024-10-03 02:12:28 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:28 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-03 02:12:28 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-03 02:12:28 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jQlcZKrykP/ea_profile.json
* 2024-10-03 02:12:32 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jQlcZKrykP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-03 02:12:32 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-04 02:12:14 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-04 02:12:15 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-04 02:12:16 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-04 02:12:16 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-04 02:12:16 (7668) [[32mINFO[0m] 
* 2024-10-04 02:12:21 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-04 02:12:21 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-04 02:12:21 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-04 02:12:21 (7668) [[32mINFO[0m] 
* 2024-10-04 02:12:21 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-04 02:12:21 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-04 02:12:21 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-04 02:12:21 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-04 02:12:21 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-04 02:12:21 (7698) [[32mINFO[0m] 
* 2024-10-04 02:12:22 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-04 02:12:22 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-04 02:12:23 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-04 02:12:23 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_eh9sei6O9/ea_profile.json
* 2024-10-04 02:12:26 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_eh9sei6O9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-04 02:12:26 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-04 15:46:12 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-04 15:46:13 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-04 15:46:14 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-04 15:46:14 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-04 15:46:14 (7668) [[32mINFO[0m] 
* 2024-10-04 15:46:48 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-04 15:46:48 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-04 15:46:48 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-04 15:46:48 (7668) [[32mINFO[0m] 
* 2024-10-04 15:46:48 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-04 15:46:48 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-04 15:46:48 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-04 15:46:48 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-04 15:46:48 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-04 15:46:48 (7698) [[32mINFO[0m] 
* 2024-10-04 15:47:09 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-04 15:47:09 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-04 15:47:09 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-04 15:47:09 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vBJGFOrwYz/ea_profile.json
* 2024-10-04 15:47:12 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vBJGFOrwYz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-04 15:47:12 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-05 02:13:22 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-05 02:13:23 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-05 02:13:24 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-05 02:13:24 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-05 02:13:24 (7668) [[32mINFO[0m] 
* 2024-10-05 02:13:30 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-05 02:13:30 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-05 02:13:30 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-05 02:13:30 (7668) [[32mINFO[0m] 
* 2024-10-05 02:13:30 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-05 02:13:30 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-05 02:13:30 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-05 02:13:30 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-05 02:13:30 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-05 02:13:30 (7698) [[32mINFO[0m] 
* 2024-10-05 02:13:33 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:13:33 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-05 02:13:33 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-05 02:13:33 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vMvWFiJADm/ea_profile.json
* 2024-10-05 02:13:37 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vMvWFiJADm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-05 02:13:37 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-06 02:14:52 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-06 02:14:52 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-06 02:14:54 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-06 02:14:54 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-06 02:14:54 (7668) [[32mINFO[0m] 
* 2024-10-06 02:15:02 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-06 02:15:02 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-06 02:15:02 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-06 02:15:02 (7668) [[32mINFO[0m] 
* 2024-10-06 02:15:02 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-06 02:15:02 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-06 02:15:02 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-06 02:15:02 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-06 02:15:02 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-06 02:15:02 (7698) [[32mINFO[0m] 
* 2024-10-06 02:15:05 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:15:05 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-06 02:15:06 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-06 02:15:06 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/bb8in_5BLB/ea_profile.json
* 2024-10-06 02:15:10 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/bb8in_5BLB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-06 02:15:10 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-07 02:12:06 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-07 02:12:06 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-07 02:12:08 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-07 02:12:08 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-07 02:12:08 (7668) [[32mINFO[0m] 
* 2024-10-07 02:12:12 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-07 02:12:12 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-07 02:12:12 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-07 02:12:12 (7668) [[32mINFO[0m] 
* 2024-10-07 02:12:12 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-07 02:12:12 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-07 02:12:12 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-07 02:12:12 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-07 02:12:12 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-07 02:12:12 (7698) [[32mINFO[0m] 
* 2024-10-07 02:12:14 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-07 02:12:14 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-07 02:12:14 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-07 02:12:14 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ypAWEDWvfZ/ea_profile.json
* 2024-10-07 02:12:18 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ypAWEDWvfZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-07 02:12:18 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-08 02:12:08 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-08 02:12:09 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-08 02:12:10 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-08 02:12:10 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-08 02:12:10 (7668) [[32mINFO[0m] 
* 2024-10-08 02:12:14 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-08 02:12:14 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-08 02:12:14 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-08 02:12:14 (7668) [[32mINFO[0m] 
* 2024-10-08 02:12:14 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-08 02:12:14 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-08 02:12:14 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-08 02:12:14 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-08 02:12:14 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-08 02:12:14 (7698) [[32mINFO[0m] 
* 2024-10-08 02:12:15 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:15 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-08 02:12:16 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-08 02:12:16 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/w1f52GfXtG/ea_profile.json
* 2024-10-08 02:12:19 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/w1f52GfXtG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-08 02:12:19 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-09 02:12:10 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-09 02:12:11 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-09 02:12:12 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-09 02:12:12 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-09 02:12:12 (7668) [[32mINFO[0m] 
* 2024-10-09 02:12:17 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-09 02:12:17 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-09 02:12:17 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-09 02:12:17 (7668) [[32mINFO[0m] 
* 2024-10-09 02:12:18 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-09 02:12:18 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-09 02:12:18 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-09 02:12:18 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-09 02:12:18 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-09 02:12:18 (7698) [[32mINFO[0m] 
* 2024-10-09 02:12:19 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-09 02:12:19 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-09 02:12:20 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-09 02:12:20 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/I09Vy_XhXY/ea_profile.json
* 2024-10-09 02:12:23 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/I09Vy_XhXY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-09 02:12:23 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-10 02:12:25 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-10 02:12:25 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-10 02:12:27 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-10 02:12:27 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-10 02:12:27 (7668) [[32mINFO[0m] 
* 2024-10-10 02:12:31 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-10 02:12:31 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-10 02:12:31 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-10 02:12:31 (7668) [[32mINFO[0m] 
* 2024-10-10 02:12:31 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-10 02:12:31 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-10 02:12:31 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-10 02:12:31 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-10 02:12:31 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-10 02:12:31 (7698) [[32mINFO[0m] 
* 2024-10-10 02:12:32 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-10 02:12:32 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-10 02:12:32 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-10 02:12:32 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XzqEjgAFfH/ea_profile.json
* 2024-10-10 02:12:41 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XzqEjgAFfH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-10 02:12:41 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-11 02:12:09 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-11 02:12:09 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-11 02:12:11 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-11 02:12:11 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-11 02:12:11 (7668) [[32mINFO[0m] 
* 2024-10-11 02:12:15 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-11 02:12:15 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-11 02:12:15 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-11 02:12:15 (7668) [[32mINFO[0m] 
* 2024-10-11 02:12:15 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-11 02:12:15 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-11 02:12:15 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-11 02:12:15 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-11 02:12:15 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-11 02:12:15 (7698) [[32mINFO[0m] 
* 2024-10-11 02:12:16 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:16 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-11 02:12:16 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-11 02:12:16 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mECOj16yh5/ea_profile.json
* 2024-10-11 02:12:19 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mECOj16yh5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-11 02:12:19 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-12 02:12:43 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-12 02:12:44 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-12 02:12:45 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-12 02:12:45 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-12 02:12:45 (7668) [[32mINFO[0m] 
* 2024-10-12 02:13:18 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-12 02:13:18 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-12 02:13:18 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-12 02:13:18 (7668) [[32mINFO[0m] 
* 2024-10-12 02:13:18 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-12 02:13:18 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-12 02:13:18 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-12 02:13:18 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-12 02:13:18 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-12 02:13:18 (7698) [[32mINFO[0m] 
* 2024-10-12 02:13:20 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:13:20 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-12 02:13:21 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-12 02:13:21 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IjH3FdJ41E/ea_profile.json
* 2024-10-12 02:13:24 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IjH3FdJ41E/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-12 02:13:24 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-13 02:12:31 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-13 02:12:32 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-13 02:12:33 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-13 02:12:33 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-13 02:12:33 (7668) [[32mINFO[0m] 
* 2024-10-13 02:12:37 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-13 02:12:37 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-13 02:12:37 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-13 02:12:37 (7668) [[32mINFO[0m] 
* 2024-10-13 02:12:37 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-13 02:12:37 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-13 02:12:37 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-13 02:12:37 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-13 02:12:37 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-13 02:12:37 (7698) [[32mINFO[0m] 
* 2024-10-13 02:12:39 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:39 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-13 02:12:39 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-13 02:12:39 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CZBEJAVo7q/ea_profile.json
* 2024-10-13 02:12:41 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CZBEJAVo7q/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-13 02:12:41 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-14 02:12:07 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-14 02:12:08 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-14 02:12:09 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-14 02:12:09 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-14 02:12:09 (7668) [[32mINFO[0m] 
* 2024-10-14 02:12:12 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-14 02:12:12 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-14 02:12:12 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-14 02:12:12 (7668) [[32mINFO[0m] 
* 2024-10-14 02:12:13 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-14 02:12:13 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-14 02:12:13 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-14 02:12:13 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-14 02:12:13 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-14 02:12:13 (7698) [[32mINFO[0m] 
* 2024-10-14 02:12:14 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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 02:12:14 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-14 02:12:14 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-14 02:12:14 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/g5iwKXIIYz/ea_profile.json
* 2024-10-14 02:12:16 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/g5iwKXIIYz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-14 02:12:16 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-15 02:12:06 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-15 02:12:06 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-15 02:12:07 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-15 02:12:07 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-15 02:12:07 (7668) [[32mINFO[0m] 
* 2024-10-15 02:12:12 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-15 02:12:12 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-15 02:12:12 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-15 02:12:12 (7668) [[32mINFO[0m] 
* 2024-10-15 02:12:12 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-15 02:12:12 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-15 02:12:12 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-15 02:12:12 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-15 02:12:12 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-15 02:12:12 (7698) [[32mINFO[0m] 
* 2024-10-15 02:12:13 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-15 02:12:13 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-15 02:12:13 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-15 02:12:13 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/17O2Zepdzc/ea_profile.json
* 2024-10-15 02:12:16 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/17O2Zepdzc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-15 02:12:16 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-16 02:12:11 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-16 02:12:11 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-16 02:12:12 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-16 02:12:12 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-16 02:12:12 (7668) [[32mINFO[0m] 
* 2024-10-16 02:12:18 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-16 02:12:18 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-16 02:12:18 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-16 02:12:18 (7668) [[32mINFO[0m] 
* 2024-10-16 02:12:19 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-16 02:12:19 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-16 02:12:19 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-16 02:12:19 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-16 02:12:19 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-16 02:12:19 (7698) [[32mINFO[0m] 
* 2024-10-16 02:12:22 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:22 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-16 02:12:22 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-16 02:12:22 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Rqn_WJ92aP/ea_profile.json
* 2024-10-16 02:12:26 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Rqn_WJ92aP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-16 02:12:26 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-17 02:12:17 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-17 02:12:17 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-17 02:12:18 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-17 02:12:18 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-17 02:12:18 (7668) [[32mINFO[0m] 
* 2024-10-17 02:12:21 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-17 02:12:21 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-17 02:12:21 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-17 02:12:21 (7668) [[32mINFO[0m] 
* 2024-10-17 02:12:22 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-17 02:12:22 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-17 02:12:22 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-17 02:12:22 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-17 02:12:22 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-17 02:12:22 (7698) [[32mINFO[0m] 
* 2024-10-17 02:12:23 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-17 02:12:23 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-17 02:12:23 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-17 02:12:23 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YlvqCHzCPE/ea_profile.json
* 2024-10-17 02:12:26 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YlvqCHzCPE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-17 02:12:26 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-18 02:14:38 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-18 02:14:39 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-18 02:14:40 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-18 02:14:40 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-18 02:14:40 (7668) [[32mINFO[0m] 
* 2024-10-18 02:14:46 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-18 02:14:46 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-18 02:14:46 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-18 02:14:46 (7668) [[32mINFO[0m] 
* 2024-10-18 02:14:46 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-18 02:14:46 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-18 02:14:46 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-18 02:14:46 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-18 02:14:46 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-18 02:14:46 (7698) [[32mINFO[0m] 
* 2024-10-18 02:14:49 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-18 02:14:49 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-18 02:14:49 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-18 02:14:49 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/O6taKAUDgB/ea_profile.json
* 2024-10-18 02:14:53 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/O6taKAUDgB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-18 02:14:53 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-18 15:46:25 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-18 15:46:25 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-18 15:46:27 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-18 15:46:27 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-18 15:46:27 (7668) [[32mINFO[0m] 
* 2024-10-18 15:46:30 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-18 15:46:30 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-18 15:46:30 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-18 15:46:30 (7668) [[32mINFO[0m] 
* 2024-10-18 15:46:30 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-18 15:46:30 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-18 15:46:30 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-18 15:46:30 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-18 15:46:30 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-18 15:46:30 (7698) [[32mINFO[0m] 
* 2024-10-18 15:46:31 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-18 15:46:31 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-18 15:46:31 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-18 15:46:31 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tS9ttXvyOy/ea_profile.json
* 2024-10-18 15:46:34 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tS9ttXvyOy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-18 15:46:34 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-19 02:12:30 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-19 02:12:31 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-19 02:12:32 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-19 02:12:32 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-19 02:12:32 (7668) [[32mINFO[0m] 
* 2024-10-19 02:12:40 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-19 02:12:40 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-19 02:12:40 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-19 02:12:40 (7668) [[32mINFO[0m] 
* 2024-10-19 02:12:40 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-19 02:12:40 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-19 02:12:40 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-19 02:12:40 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-19 02:12:40 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-19 02:12:40 (7698) [[32mINFO[0m] 
* 2024-10-19 02:12:43 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-19 02:12:43 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-19 02:12:44 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-19 02:12:44 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BDQ8hHyL5k/ea_profile.json
* 2024-10-19 02:12:49 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BDQ8hHyL5k/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-19 02:12:49 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-20 02:12:33 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-20 02:12:34 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-20 02:12:35 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-20 02:12:36 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-20 02:12:36 (7668) [[32mINFO[0m] 
* 2024-10-20 02:12:40 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-20 02:12:40 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-20 02:12:40 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-20 02:12:40 (7668) [[32mINFO[0m] 
* 2024-10-20 02:12:40 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-20 02:12:40 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-20 02:12:40 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-20 02:12:40 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-20 02:12:40 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-20 02:12:40 (7698) [[32mINFO[0m] 
* 2024-10-20 02:12:41 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-20 02:12:41 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-20 02:12:42 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-20 02:12:42 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/stRAp5iEZI/ea_profile.json
* 2024-10-20 02:12:45 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/stRAp5iEZI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-20 02:12:45 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-21 02:13:57 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-21 02:13:58 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-21 02:13:59 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-21 02:13:59 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-21 02:13:59 (7668) [[32mINFO[0m] 
* 2024-10-21 02:14:04 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-21 02:14:04 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-21 02:14:04 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-21 02:14:04 (7668) [[32mINFO[0m] 
* 2024-10-21 02:14:04 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-21 02:14:04 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-21 02:14:04 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-21 02:14:04 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-21 02:14:04 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-21 02:14:04 (7698) [[32mINFO[0m] 
* 2024-10-21 02:14:05 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:14:05 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-21 02:14:06 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-21 02:14:06 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ud8EiB_J46/ea_profile.json
* 2024-10-21 02:14:09 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ud8EiB_J46/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-21 02:14:09 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-22 02:12:06 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-22 02:12:07 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-22 02:12:08 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-22 02:12:08 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-22 02:12:08 (7668) [[32mINFO[0m] 
* 2024-10-22 02:12:14 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-22 02:12:14 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-22 02:12:14 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-22 02:12:14 (7668) [[32mINFO[0m] 
* 2024-10-22 02:12:14 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-22 02:12:14 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-22 02:12:14 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-22 02:12:14 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-22 02:12:14 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-22 02:12:14 (7698) [[32mINFO[0m] 
* 2024-10-22 02:12:16 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-22 02:12:16 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-22 02:12:17 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-22 02:12:17 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7csoDU_fK8/ea_profile.json
* 2024-10-22 02:12:20 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7csoDU_fK8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-22 02:12:20 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-23 02:12:08 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-23 02:12:09 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-23 02:12:10 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-23 02:12:10 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-23 02:12:10 (7668) [[32mINFO[0m] 
* 2024-10-23 02:12:14 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-23 02:12:14 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-23 02:12:14 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-23 02:12:14 (7668) [[32mINFO[0m] 
* 2024-10-23 02:12:14 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-23 02:12:14 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-23 02:12:14 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-23 02:12:14 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-23 02:12:14 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-23 02:12:14 (7698) [[32mINFO[0m] 
* 2024-10-23 02:12:15 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-23 02:12:15 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-23 02:12:16 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-23 02:12:16 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6rOT6eexfh/ea_profile.json
* 2024-10-23 02:12:19 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6rOT6eexfh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-23 02:12:19 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-24 02:12:09 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-24 02:12:10 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-24 02:12:11 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-24 02:12:11 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-24 02:12:11 (7668) [[32mINFO[0m] 
* 2024-10-24 02:12:16 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-24 02:12:16 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-24 02:12:16 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-24 02:12:16 (7668) [[32mINFO[0m] 
* 2024-10-24 02:12:16 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-24 02:12:16 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-24 02:12:16 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-24 02:12:16 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-24 02:12:16 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-24 02:12:16 (7698) [[32mINFO[0m] 
* 2024-10-24 02:12:18 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-24 02:12:18 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-24 02:12:18 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-24 02:12:18 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/v0JhoN9ANf/ea_profile.json
* 2024-10-24 02:12:21 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/v0JhoN9ANf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-24 02:12:21 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-25 02:12:16 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-25 02:12:16 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-25 02:12:18 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-25 02:12:18 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-25 02:12:18 (7668) [[32mINFO[0m] 
* 2024-10-25 02:12:28 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-25 02:12:28 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-25 02:12:28 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-25 02:12:28 (7668) [[32mINFO[0m] 
* 2024-10-25 02:12:28 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-25 02:12:28 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-25 02:12:28 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-25 02:12:28 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-25 02:12:28 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-25 02:12:28 (7698) [[32mINFO[0m] 
* 2024-10-25 02:12:29 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-25 02:12:29 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-25 02:12:30 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-25 02:12:30 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4vSfZg4CIC/ea_profile.json
* 2024-10-25 02:12:33 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4vSfZg4CIC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-25 02:12:33 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-25 15:46:26 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-25 15:46:26 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-25 15:46:29 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-25 15:46:29 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-25 15:46:29 (7668) [[32mINFO[0m] 
* 2024-10-25 15:46:32 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-25 15:46:32 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-25 15:46:32 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-25 15:46:32 (7668) [[32mINFO[0m] 
* 2024-10-25 15:46:32 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-25 15:46:32 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-25 15:46:32 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-25 15:46:32 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-25 15:46:32 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-25 15:46:32 (7698) [[32mINFO[0m] 
* 2024-10-25 15:46:33 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-25 15:46:33 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-25 15:46:34 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-25 15:46:34 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iguLWFBmx9/ea_profile.json
* 2024-10-25 15:46:36 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iguLWFBmx9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-25 15:46:36 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-26 02:12:36 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-26 02:12:36 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-26 02:12:38 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-26 02:12:38 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-26 02:12:38 (7668) [[32mINFO[0m] 
* 2024-10-26 02:12:42 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-26 02:12:42 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-26 02:12:42 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-26 02:12:42 (7668) [[32mINFO[0m] 
* 2024-10-26 02:12:42 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-26 02:12:42 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-26 02:12:42 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-26 02:12:42 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-26 02:12:42 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-26 02:12:42 (7698) [[32mINFO[0m] 
* 2024-10-26 02:12:43 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:43 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-26 02:12:44 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-26 02:12:44 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9Om9mFRa3b/ea_profile.json
* 2024-10-26 02:12:47 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9Om9mFRa3b/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-26 02:12:47 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-27 02:12:35 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-27 02:12:35 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-27 02:12:37 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-27 02:12:37 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-27 02:12:37 (7668) [[32mINFO[0m] 
* 2024-10-27 02:12:40 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-27 02:12:40 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-27 02:12:40 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-27 02:12:40 (7668) [[32mINFO[0m] 
* 2024-10-27 02:12:40 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-27 02:12:40 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-27 02:12:40 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-27 02:12:40 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-27 02:12:40 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-27 02:12:40 (7698) [[32mINFO[0m] 
* 2024-10-27 02:12:41 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-27 02:12:41 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-27 02:12:41 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-27 02:12:41 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BhsAYVMFkO/ea_profile.json
* 2024-10-27 02:12:43 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BhsAYVMFkO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-27 02:12:43 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-28 02:12:14 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-28 02:12:15 (9031) [[32mINFO[0m] Script is up to date.
* 2024-10-28 02:12:17 (739) [[33mWARN[0m]  is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with  enabled.
* 2024-10-28 02:12:17 (7667) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-28 02:12:17 (7668) [[32mINFO[0m] 
* 2024-10-28 02:12:20 (1995) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-28 02:12:20 (1996) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-28 02:12:20 (7667) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-28 02:12:20 (7668) [[32mINFO[0m] 
* 2024-10-28 02:12:20 (7681) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-28 02:12:20 (7681) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-28 02:12:20 (7681) [[32mINFO[0m]               : epel extras updates
* 2024-10-28 02:12:20 (7681) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-28 02:12:20 (7681) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-28 02:12:20 (7698) [[32mINFO[0m] 
* 2024-10-28 02:12:22 (2005) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-28 02:12:22 (2006) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-28 02:12:22 (998) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-28 02:12:22 (6803) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rqpYRuBOCI/ea_profile.json
* 2024-10-28 02:12:25 (390) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rqpYRuBOCI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-28 02:12:25 (354) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-29 02:12:19 (9009) [[32mINFO[0m] Self-update of script version 55 requested.
* 2024-10-29 02:12:20 (9014) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-10-29 02:12:21 (9023) [[32mINFO[0m] Script update to version 56 successful.
* 2024-10-29 02:12:23 (3776) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-10-29 02:12:23 (7661) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-29 02:12:23 (7662) [[32mINFO[0m] 
* 2024-10-29 02:12:25 (5456) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-29 02:12:25 (5457) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-29 02:12:25 (7661) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-29 02:12:25 (7662) [[32mINFO[0m] 
* 2024-10-29 02:12:26 (7675) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-29 02:12:26 (7675) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-29 02:12:26 (7675) [[32mINFO[0m]               : epel extras updates
* 2024-10-29 02:12:26 (7675) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-29 02:12:26 (7675) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-29 02:12:26 (7692) [[32mINFO[0m] 
* 2024-10-29 02:12:27 (5466) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:27 (5467) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-29 02:12:27 (1977) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-29 02:12:27 (6797) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/c4yTfmkeMF/ea_profile.json
* 2024-10-29 02:12:30 (488) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/c4yTfmkeMF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-10-29 02:12:30 (452) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-30 02:12:27 (8998) [[32mINFO[0m] Self-update of script version 56 requested.
* 2024-10-30 02:12:27 (9020) [[32mINFO[0m] Script is up to date.
* 2024-10-30 02:12:29 (3776) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-10-30 02:12:29 (7661) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-30 02:12:29 (7662) [[32mINFO[0m] 
* 2024-10-30 02:12:33 (5456) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-30 02:12:33 (5457) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-30 02:12:33 (7661) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-30 02:12:33 (7662) [[32mINFO[0m] 
* 2024-10-30 02:12:33 (7675) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-30 02:12:33 (7675) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-30 02:12:33 (7675) [[32mINFO[0m]               : epel extras updates
* 2024-10-30 02:12:33 (7675) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-30 02:12:33 (7675) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-30 02:12:33 (7692) [[32mINFO[0m] 
* 2024-10-30 02:12:35 (5466) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-30 02:12:35 (5467) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-30 02:12:35 (1977) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-30 02:12:35 (6797) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eZD0emV5J0/ea_profile.json
* 2024-10-30 02:13:06 (488) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eZD0emV5J0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-10-30 02:13:06 (452) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-31 02:12:32 (8998) [[32mINFO[0m] Self-update of script version 56 requested.
* 2024-10-31 02:12:32 (9020) [[32mINFO[0m] Script is up to date.
* 2024-10-31 02:12:34 (3776) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-10-31 02:12:34 (7661) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-10-31 02:12:34 (7662) [[32mINFO[0m] 
* 2024-10-31 02:12:38 (5456) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-31 02:12:38 (5457) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-10-31 02:12:38 (7661) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-10-31 02:12:38 (7662) [[32mINFO[0m] 
* 2024-10-31 02:12:38 (7675) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-31 02:12:38 (7675) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-10-31 02:12:38 (7675) [[32mINFO[0m]               : epel extras updates
* 2024-10-31 02:12:38 (7675) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-10-31 02:12:38 (7675) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-10-31 02:12:38 (7692) [[32mINFO[0m] 
* 2024-10-31 02:12:40 (5466) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:40 (5467) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-10-31 02:12:40 (1977) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-31 02:12:40 (6797) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/96VRlBiZT6/ea_profile.json
* 2024-10-31 02:13:10 (488) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/96VRlBiZT6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-10-31 02:13:10 (452) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-01 02:12:37 (8998) [[32mINFO[0m] Self-update of script version 56 requested.
* 2024-11-01 02:12:38 (9020) [[32mINFO[0m] Script is up to date.
* 2024-11-01 02:12:39 (3776) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-01 02:12:39 (7661) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-01 02:12:39 (7662) [[32mINFO[0m] 
* 2024-11-01 02:12:43 (5456) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-01 02:12:43 (5457) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-01 02:12:43 (7661) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-01 02:12:43 (7662) [[32mINFO[0m] 
* 2024-11-01 02:12:43 (7675) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-01 02:12:44 (7675) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-01 02:12:44 (7675) [[32mINFO[0m]               : epel extras updates
* 2024-11-01 02:12:44 (7675) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-01 02:12:44 (7675) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-01 02:12:44 (7692) [[32mINFO[0m] 
* 2024-11-01 02:12:45 (5466) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-01 02:12:45 (5467) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-01 02:12:46 (1977) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-01 02:12:46 (6797) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/w8mTLJHP55/ea_profile.json
* 2024-11-01 02:12:49 (488) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/w8mTLJHP55/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-01 02:12:49 (452) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-01 15:46:44 (8998) [[32mINFO[0m] Self-update of script version 56 requested.
* 2024-11-01 15:46:45 (9020) [[32mINFO[0m] Script is up to date.
* 2024-11-01 15:46:46 (3776) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-01 15:46:46 (7661) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-01 15:46:46 (7662) [[32mINFO[0m] 
* 2024-11-01 15:46:49 (5456) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-01 15:46:49 (5457) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-01 15:46:49 (7661) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-01 15:46:49 (7662) [[32mINFO[0m] 
* 2024-11-01 15:46:49 (7675) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-01 15:46:49 (7675) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-01 15:46:49 (7675) [[32mINFO[0m]               : epel extras updates
* 2024-11-01 15:46:49 (7675) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-01 15:46:49 (7675) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-01 15:46:49 (7692) [[32mINFO[0m] 
* 2024-11-01 15:46:50 (5466) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-01 15:46:50 (5467) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-01 15:46:50 (1977) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-01 15:46:50 (6797) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AF8SNSrgNt/ea_profile.json
* 2024-11-01 15:46:53 (488) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AF8SNSrgNt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-01 15:46:53 (452) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-02 02:12:59 (8998) [[32mINFO[0m] Self-update of script version 56 requested.
* 2024-11-02 02:13:00 (9020) [[32mINFO[0m] Script is up to date.
* 2024-11-02 02:13:01 (3776) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-02 02:13:01 (7661) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-02 02:13:01 (7662) [[32mINFO[0m] 
* 2024-11-02 02:13:04 (5456) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-02 02:13:04 (5457) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-02 02:13:04 (7661) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-02 02:13:04 (7662) [[32mINFO[0m] 
* 2024-11-02 02:13:05 (7675) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-02 02:13:05 (7675) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-02 02:13:05 (7675) [[32mINFO[0m]               : epel extras updates
* 2024-11-02 02:13:05 (7675) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-02 02:13:05 (7675) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-02 02:13:05 (7692) [[32mINFO[0m] 
* 2024-11-02 02:13:06 (5466) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:06 (5467) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-02 02:13:06 (1977) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-02 02:13:06 (6797) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0nsNV_PinQ/ea_profile.json
* 2024-11-02 02:13:09 (488) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0nsNV_PinQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-02 02:13:09 (452) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-03 02:13:06 (8998) [[32mINFO[0m] Self-update of script version 56 requested.
* 2024-11-03 02:13:07 (9020) [[32mINFO[0m] Script is up to date.
* 2024-11-03 02:13:08 (3776) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-03 02:13:08 (7661) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-03 02:13:08 (7662) [[32mINFO[0m] 
* 2024-11-03 02:13:13 (5456) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-03 02:13:13 (5457) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-03 02:13:13 (7661) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-03 02:13:13 (7662) [[32mINFO[0m] 
* 2024-11-03 02:13:13 (7675) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-03 02:13:13 (7675) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-03 02:13:13 (7675) [[32mINFO[0m]               : epel extras updates
* 2024-11-03 02:13:13 (7675) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-03 02:13:13 (7675) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-03 02:13:13 (7692) [[32mINFO[0m] 
* 2024-11-03 02:13:14 (5466) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-03 02:13:14 (5467) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-03 02:13:15 (1977) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-03 02:13:15 (6797) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ShMtRXgUQg/ea_profile.json
* 2024-11-03 02:13:19 (488) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ShMtRXgUQg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-03 02:13:19 (452) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-04 02:13:50 (8998) [[32mINFO[0m] Self-update of script version 56 requested.
* 2024-11-04 02:13:50 (9020) [[32mINFO[0m] Script is up to date.
* 2024-11-04 02:13:52 (3776) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-04 02:13:52 (7661) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-04 02:13:52 (7662) [[32mINFO[0m] 
* 2024-11-04 02:13:59 (5456) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-04 02:13:59 (5457) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-04 02:13:59 (7661) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-04 02:13:59 (7662) [[32mINFO[0m] 
* 2024-11-04 02:13:59 (7675) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-04 02:13:59 (7675) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-04 02:13:59 (7675) [[32mINFO[0m]               : epel extras updates
* 2024-11-04 02:13:59 (7675) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-04 02:13:59 (7675) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-04 02:13:59 (7692) [[32mINFO[0m] 
* 2024-11-04 02:14:01 (5466) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:14:01 (5467) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-04 02:14:01 (1977) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-04 02:14:01 (6797) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IxXNMWoL9t/ea_profile.json
* 2024-11-04 02:14:17 (488) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IxXNMWoL9t/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-04 02:14:17 (452) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-05 02:12:11 (8998) [[32mINFO[0m] Self-update of script version 56 requested.
* 2024-11-05 02:12:11 (9020) [[32mINFO[0m] Script is up to date.
* 2024-11-05 02:12:13 (3776) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-05 02:12:13 (7661) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-05 02:12:13 (7662) [[32mINFO[0m] 
* 2024-11-05 02:12:17 (5456) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-05 02:12:17 (5457) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-05 02:12:17 (7661) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-05 02:12:17 (7662) [[32mINFO[0m] 
* 2024-11-05 02:12:17 (7675) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-05 02:12:17 (7675) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-05 02:12:17 (7675) [[32mINFO[0m]               : epel extras updates
* 2024-11-05 02:12:17 (7675) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-05 02:12:17 (7675) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-05 02:12:17 (7692) [[32mINFO[0m] 
* 2024-11-05 02:12:19 (5466) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:19 (5467) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-05 02:12:19 (1977) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-05 02:12:19 (6797) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fHTAZ2YdGD/ea_profile.json
* 2024-11-05 02:12:23 (488) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fHTAZ2YdGD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-05 02:12:23 (452) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-06 02:12:15 (8998) [[32mINFO[0m] Self-update of script version 56 requested.
* 2024-11-06 02:12:16 (9020) [[32mINFO[0m] Script is up to date.
* 2024-11-06 02:12:17 (3776) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-06 02:12:17 (7661) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-06 02:12:17 (7662) [[32mINFO[0m] 
* 2024-11-06 02:12:22 (5456) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-06 02:12:22 (5457) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-06 02:12:22 (7661) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-06 02:12:22 (7662) [[32mINFO[0m] 
* 2024-11-06 02:12:22 (7675) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-06 02:12:22 (7675) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-06 02:12:22 (7675) [[32mINFO[0m]               : epel extras updates
* 2024-11-06 02:12:22 (7675) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-06 02:12:22 (7675) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-06 02:12:22 (7692) [[32mINFO[0m] 
* 2024-11-06 02:12:23 (5466) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-06 02:12:23 (5467) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-06 02:12:24 (1977) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-06 02:12:24 (6797) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fJuxAMeYY_/ea_profile.json
* 2024-11-06 02:12:28 (488) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fJuxAMeYY_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-06 02:12:28 (452) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-07 02:12:34 (8998) [[32mINFO[0m] Self-update of script version 56 requested.
* 2024-11-07 02:12:34 (9020) [[32mINFO[0m] Script is up to date.
* 2024-11-07 02:12:36 (3776) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-07 02:12:36 (7661) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-07 02:12:36 (7662) [[32mINFO[0m] 
* 2024-11-07 02:12:40 (5456) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-07 02:12:40 (5457) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-07 02:12:40 (7661) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-07 02:12:40 (7662) [[32mINFO[0m] 
* 2024-11-07 02:12:41 (7675) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-07 02:12:41 (7675) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-07 02:12:41 (7675) [[32mINFO[0m]               : epel extras updates
* 2024-11-07 02:12:41 (7675) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-07 02:12:41 (7675) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-07 02:12:41 (7692) [[32mINFO[0m] 
* 2024-11-07 02:12:42 (5466) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-07 02:12:42 (5467) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-07 02:12:43 (1977) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-07 02:12:43 (6797) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qdfwz4NB_Q/ea_profile.json
* 2024-11-07 02:12:46 (488) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qdfwz4NB_Q/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-07 02:12:46 (452) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-08 02:12:32 (8998) [[32mINFO[0m] Self-update of script version 56 requested.
* 2024-11-08 02:12:32 (9020) [[32mINFO[0m] Script is up to date.
* 2024-11-08 02:12:33 (3776) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-08 02:12:33 (7661) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-08 02:12:33 (7662) [[32mINFO[0m] 
* 2024-11-08 02:12:37 (5456) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-08 02:12:37 (5457) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-08 02:12:37 (7661) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-08 02:12:37 (7662) [[32mINFO[0m] 
* 2024-11-08 02:12:37 (7675) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-08 02:12:38 (7675) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-08 02:12:38 (7675) [[32mINFO[0m]               : epel extras updates
* 2024-11-08 02:12:38 (7675) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-08 02:12:38 (7675) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-08 02:12:38 (7692) [[32mINFO[0m] 
* 2024-11-08 02:12:39 (5466) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-08 02:12:39 (5467) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-08 02:12:39 (1977) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-08 02:12:39 (6797) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/geoW5UeFVY/ea_profile.json
* 2024-11-08 02:12:43 (488) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/geoW5UeFVY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-08 02:12:43 (452) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-08 15:46:39 (8998) [[32mINFO[0m] Self-update of script version 56 requested.
* 2024-11-08 15:46:39 (9003) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-11-08 15:46:40 (9012) [[32mINFO[0m] Script update to version 57 successful.
* 2024-11-08 15:46:42 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-08 15:46:42 (8440) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-08 15:46:42 (8441) [[32mINFO[0m] 
* 2024-11-08 15:46:51 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-08 15:46:51 (8441) [[32mINFO[0m] 
* 2024-11-08 15:46:51 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-08 15:46:51 (8454) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]         or
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]         compromise:
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-08 15:47:07 (8471) [[32mINFO[0m] 
* 2024-11-08 15:47:07 (5507) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-08 15:47:07 (5508) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-08 15:47:07 (8440) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-08 15:47:07 (8441) [[32mINFO[0m] 
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m]               : epel extras updates
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-08 15:47:07 (8471) [[32mINFO[0m] 
* 2024-11-08 15:47:07 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-08 15:47:07 (8441) [[32mINFO[0m] 
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-08 15:47:07 (8454) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m] 14: HTTP Error 500 - Internal Server Error
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]         or
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]         compromise:
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m] 
* 2024-11-08 15:47:11 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2024-11-08 15:47:11 (8471) [[32mINFO[0m] 
* 2024-11-08 15:47:11 (5517) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-08 15:47:11 (5518) [[31mERROR[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
14: HTTP Error 500 - Internal Server Error


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2024-11-08 15:47:11 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-08 15:47:11 (7581) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/v7PK5kmts9/ea_profile.json
* 2024-11-08 15:47:12 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/v7PK5kmts9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-08 15:47:12 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-09 02:13:22 (9491) [[32mINFO[0m] Self-update of script version 57 requested.
* 2024-11-09 02:13:22 (9513) [[32mINFO[0m] Script is up to date.
* 2024-11-09 02:13:24 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-09 02:13:24 (8440) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-09 02:13:24 (8441) [[32mINFO[0m] 
* 2024-11-09 02:13:27 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-09 02:13:27 (8441) [[32mINFO[0m] 
* 2024-11-09 02:13:27 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-09 02:13:27 (8454) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]         or
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]         compromise:
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-09 02:13:30 (8471) [[32mINFO[0m] 
* 2024-11-09 02:13:30 (5507) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-09 02:13:30 (5508) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-09 02:13:30 (8440) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-09 02:13:30 (8441) [[32mINFO[0m] 
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m]               : epel extras updates
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-09 02:13:30 (8471) [[32mINFO[0m] 
* 2024-11-09 02:13:30 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-09 02:13:30 (8441) [[32mINFO[0m] 
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-09 02:13:30 (8454) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]         or
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]         compromise:
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m] 
* 2024-11-09 02:13:32 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-09 02:13:32 (8471) [[32mINFO[0m] 
* 2024-11-09 02:13:32 (5517) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-09 02:13:32 (5518) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-09 02:13:33 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-09 02:13:33 (7581) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Df8fH2tqoz/ea_profile.json
* 2024-11-09 02:13:37 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Df8fH2tqoz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-09 02:13:37 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-10 02:13:19 (9491) [[32mINFO[0m] Self-update of script version 57 requested.
* 2024-11-10 02:13:20 (9513) [[32mINFO[0m] Script is up to date.
* 2024-11-10 02:13:21 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-10 02:13:21 (8440) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-10 02:13:21 (8441) [[32mINFO[0m] 
* 2024-11-10 02:13:25 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-10 02:13:25 (8441) [[32mINFO[0m] 
* 2024-11-10 02:13:25 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-10 02:13:25 (8454) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]         or
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]         compromise:
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-10 02:13:27 (8471) [[32mINFO[0m] 
* 2024-11-10 02:13:27 (5507) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-10 02:13:27 (5508) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-10 02:13:27 (8440) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-10 02:13:27 (8441) [[32mINFO[0m] 
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m]               : epel extras updates
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-10 02:13:27 (8454) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-10 02:13:27 (8471) [[32mINFO[0m] 
* 2024-11-10 02:13:27 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-10 02:13:27 (8441) [[32mINFO[0m] 
* 2024-11-10 02:13:28 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-10 02:13:28 (8454) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]         or
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]         compromise:
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-10 02:13:30 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-10 02:13:30 (8471) [[32mINFO[0m] 
* 2024-11-10 02:13:30 (5517) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:13:30 (5518) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-10 02:13:30 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-10 02:13:30 (7581) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rtnUEWZEFN/ea_profile.json
* 2024-11-10 02:13:34 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rtnUEWZEFN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-10 02:13:34 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-11 02:12:53 (9491) [[32mINFO[0m] Self-update of script version 57 requested.
* 2024-11-11 02:12:53 (9513) [[32mINFO[0m] Script is up to date.
* 2024-11-11 02:12:55 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-11 02:12:55 (8440) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-11 02:12:55 (8441) [[32mINFO[0m] 
* 2024-11-11 02:12:59 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-11 02:12:59 (8441) [[32mINFO[0m] 
* 2024-11-11 02:13:00 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-11 02:13:00 (8454) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]         or
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]         compromise:
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-11 02:13:03 (8471) [[32mINFO[0m] 
* 2024-11-11 02:13:03 (5507) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-11 02:13:03 (5508) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-11 02:13:03 (8440) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-11 02:13:03 (8441) [[32mINFO[0m] 
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m]               : epel extras updates
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-11 02:13:03 (8471) [[32mINFO[0m] 
* 2024-11-11 02:13:03 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-11 02:13:03 (8441) [[32mINFO[0m] 
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-11 02:13:03 (8454) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]         or
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]         compromise:
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-11 02:13:06 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-11 02:13:06 (8471) [[32mINFO[0m] 
* 2024-11-11 02:13:06 (5517) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:13:06 (5518) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-11 02:13:06 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-11 02:13:06 (7581) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tImnew7Ata/ea_profile.json
* 2024-11-11 02:13:11 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tImnew7Ata/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-11 02:13:11 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-12 02:13:12 (9491) [[32mINFO[0m] Self-update of script version 57 requested.
* 2024-11-12 02:13:13 (9513) [[32mINFO[0m] Script is up to date.
* 2024-11-12 02:13:14 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-12 02:13:14 (8440) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-12 02:13:14 (8441) [[32mINFO[0m] 
* 2024-11-12 02:13:16 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-12 02:13:16 (8441) [[32mINFO[0m] 
* 2024-11-12 02:13:17 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-12 02:13:17 (8454) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]         or
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]         compromise:
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-12 02:13:18 (8471) [[32mINFO[0m] 
* 2024-11-12 02:13:18 (5507) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-12 02:13:18 (5508) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-12 02:13:18 (8440) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-12 02:13:18 (8441) [[32mINFO[0m] 
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m]               : epel extras updates
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-12 02:13:18 (8471) [[32mINFO[0m] 
* 2024-11-12 02:13:18 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-12 02:13:18 (8441) [[32mINFO[0m] 
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-12 02:13:18 (8454) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]         or
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]         compromise:
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m] 
* 2024-11-12 02:13:19 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-12 02:13:19 (8471) [[32mINFO[0m] 
* 2024-11-12 02:13:19 (5517) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-12 02:13:19 (5518) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-12 02:13:20 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-12 02:13:20 (7581) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CbZLfpdTJz/ea_profile.json
* 2024-11-12 02:13:22 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CbZLfpdTJz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-12 02:13:22 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-13 02:12:54 (9491) [[32mINFO[0m] Self-update of script version 57 requested.
* 2024-11-13 02:12:55 (9513) [[32mINFO[0m] Script is up to date.
* 2024-11-13 02:12:56 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-13 02:12:56 (8440) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-13 02:12:56 (8441) [[32mINFO[0m] 
* 2024-11-13 02:12:59 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-13 02:12:59 (8441) [[32mINFO[0m] 
* 2024-11-13 02:12:59 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-13 02:12:59 (8454) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]         or
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]         compromise:
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:00 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-13 02:13:00 (8471) [[32mINFO[0m] 
* 2024-11-13 02:13:00 (5507) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-13 02:13:00 (5508) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-13 02:13:00 (8440) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-13 02:13:00 (8441) [[32mINFO[0m] 
* 2024-11-13 02:13:01 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-13 02:13:01 (8454) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-13 02:13:01 (8454) [[32mINFO[0m]               : epel extras updates
* 2024-11-13 02:13:01 (8454) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-13 02:13:01 (8454) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-13 02:13:01 (8471) [[32mINFO[0m] 
* 2024-11-13 02:13:01 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-13 02:13:01 (8441) [[32mINFO[0m] 
* 2024-11-13 02:13:01 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-13 02:13:01 (8454) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]         or
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]         compromise:
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m] 
* 2024-11-13 02:13:02 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-13 02:13:02 (8471) [[32mINFO[0m] 
* 2024-11-13 02:13:02 (5517) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:13:02 (5518) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-13 02:13:03 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-13 02:13:03 (7581) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/O9boOsP0UA/ea_profile.json
* 2024-11-13 02:13:06 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/O9boOsP0UA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-13 02:13:06 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-14 02:12:53 (9491) [[32mINFO[0m] Self-update of script version 57 requested.
* 2024-11-14 02:12:54 (9513) [[32mINFO[0m] Script is up to date.
* 2024-11-14 02:12:55 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-14 02:12:55 (8440) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-14 02:12:55 (8441) [[32mINFO[0m] 
* 2024-11-14 02:12:57 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-14 02:12:57 (8441) [[32mINFO[0m] 
* 2024-11-14 02:12:58 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-14 02:12:58 (8454) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]         or
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]         compromise:
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-14 02:12:59 (8471) [[32mINFO[0m] 
* 2024-11-14 02:12:59 (5507) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-14 02:12:59 (5508) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-14 02:12:59 (8440) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-14 02:12:59 (8441) [[32mINFO[0m] 
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m]               : epel extras updates
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-14 02:12:59 (8471) [[32mINFO[0m] 
* 2024-11-14 02:12:59 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-14 02:12:59 (8441) [[32mINFO[0m] 
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-14 02:12:59 (8454) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]         or
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]         compromise:
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m] 
* 2024-11-14 02:13:00 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-14 02:13:00 (8471) [[32mINFO[0m] 
* 2024-11-14 02:13:00 (5517) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-14 02:13:00 (5518) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-14 02:13:01 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-14 02:13:01 (7581) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qDJfmaimG1/ea_profile.json
* 2024-11-14 02:13:04 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qDJfmaimG1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-14 02:13:04 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-15 02:12:56 (9491) [[32mINFO[0m] Self-update of script version 57 requested.
* 2024-11-15 02:12:56 (9513) [[32mINFO[0m] Script is up to date.
* 2024-11-15 02:12:58 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-15 02:12:58 (8440) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-15 02:12:58 (8441) [[32mINFO[0m] 
* 2024-11-15 02:13:00 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-15 02:13:00 (8441) [[32mINFO[0m] 
* 2024-11-15 02:13:00 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-15 02:13:00 (8454) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]         or
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]         compromise:
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-15 02:13:01 (8471) [[32mINFO[0m] 
* 2024-11-15 02:13:01 (5507) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-15 02:13:01 (5508) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-15 02:13:01 (8440) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-15 02:13:01 (8441) [[32mINFO[0m] 
* 2024-11-15 02:13:01 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-15 02:13:02 (8454) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-15 02:13:02 (8454) [[32mINFO[0m]               : epel extras updates
* 2024-11-15 02:13:02 (8454) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-15 02:13:02 (8454) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-15 02:13:02 (8471) [[32mINFO[0m] 
* 2024-11-15 02:13:02 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-15 02:13:02 (8441) [[32mINFO[0m] 
* 2024-11-15 02:13:02 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-15 02:13:02 (8454) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]         or
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]         compromise:
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m] 
* 2024-11-15 02:13:03 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-15 02:13:03 (8471) [[32mINFO[0m] 
* 2024-11-15 02:13:03 (5517) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:13:03 (5518) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-15 02:13:03 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-15 02:13:03 (7581) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zIdCKFtpQM/ea_profile.json
* 2024-11-15 02:13:06 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zIdCKFtpQM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-15 02:13:06 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-15 15:47:09 (9491) [[32mINFO[0m] Self-update of script version 57 requested.
* 2024-11-15 15:47:10 (9513) [[32mINFO[0m] Script is up to date.
* 2024-11-15 15:47:11 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-15 15:47:11 (8440) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-15 15:47:11 (8441) [[32mINFO[0m] 
* 2024-11-15 15:47:15 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-15 15:47:15 (8441) [[32mINFO[0m] 
* 2024-11-15 15:47:15 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-15 15:47:15 (8454) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]         or
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]         compromise:
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:17 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-15 15:47:17 (8471) [[32mINFO[0m] 
* 2024-11-15 15:47:17 (5507) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-15 15:47:17 (5508) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-15 15:47:17 (8440) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-15 15:47:17 (8441) [[32mINFO[0m] 
* 2024-11-15 15:47:18 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-15 15:47:18 (8454) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-15 15:47:18 (8454) [[32mINFO[0m]               : epel extras updates
* 2024-11-15 15:47:18 (8454) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-15 15:47:18 (8454) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-15 15:47:18 (8471) [[32mINFO[0m] 
* 2024-11-15 15:47:18 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-15 15:47:18 (8441) [[32mINFO[0m] 
* 2024-11-15 15:47:18 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-15 15:47:18 (8454) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]         or
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]         compromise:
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m] 
* 2024-11-15 15:47:20 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-15 15:47:20 (8471) [[32mINFO[0m] 
* 2024-11-15 15:47:20 (5517) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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 15:47:20 (5518) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-15 15:47:21 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-15 15:47:21 (7581) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xiw9G3wvXA/ea_profile.json
* 2024-11-15 15:47:25 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xiw9G3wvXA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-15 15:47:25 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-16 02:13:23 (9491) [[32mINFO[0m] Self-update of script version 57 requested.
* 2024-11-16 02:13:23 (9513) [[32mINFO[0m] Script is up to date.
* 2024-11-16 02:13:25 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-16 02:13:25 (8440) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-16 02:13:25 (8441) [[32mINFO[0m] 
* 2024-11-16 02:13:27 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-16 02:13:27 (8441) [[32mINFO[0m] 
* 2024-11-16 02:13:28 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-16 02:13:28 (8454) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]         or
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]         compromise:
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-16 02:13:29 (8471) [[32mINFO[0m] 
* 2024-11-16 02:13:29 (5507) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-16 02:13:29 (5508) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-16 02:13:29 (8440) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-16 02:13:29 (8441) [[32mINFO[0m] 
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m]               : epel extras updates
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-16 02:13:29 (8471) [[32mINFO[0m] 
* 2024-11-16 02:13:29 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-16 02:13:29 (8441) [[32mINFO[0m] 
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-16 02:13:29 (8454) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]         or
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]         compromise:
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-16 02:13:30 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-16 02:13:30 (8471) [[32mINFO[0m] 
* 2024-11-16 02:13:30 (5517) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-16 02:13:30 (5518) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-16 02:13:31 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-16 02:13:31 (7581) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/izDpyg8HXc/ea_profile.json
* 2024-11-16 02:13:34 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/izDpyg8HXc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-16 02:13:34 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-17 02:13:21 (9491) [[32mINFO[0m] Self-update of script version 57 requested.
* 2024-11-17 02:13:21 (9513) [[32mINFO[0m] Script is up to date.
* 2024-11-17 02:13:23 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-17 02:13:23 (8440) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-17 02:13:23 (8441) [[32mINFO[0m] 
* 2024-11-17 02:13:26 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-17 02:13:26 (8441) [[32mINFO[0m] 
* 2024-11-17 02:13:26 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-17 02:13:26 (8454) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]         or
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]         compromise:
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-17 02:13:28 (8471) [[32mINFO[0m] 
* 2024-11-17 02:13:28 (5507) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-17 02:13:28 (5508) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-17 02:13:28 (8440) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-17 02:13:28 (8441) [[32mINFO[0m] 
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m]               : epel extras updates
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-17 02:13:28 (8471) [[32mINFO[0m] 
* 2024-11-17 02:13:28 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-17 02:13:28 (8441) [[32mINFO[0m] 
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-17 02:13:28 (8454) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]         or
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]         compromise:
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m] 
* 2024-11-17 02:13:30 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-17 02:13:30 (8471) [[32mINFO[0m] 
* 2024-11-17 02:13:30 (5517) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-17 02:13:30 (5518) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-17 02:13:30 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-17 02:13:30 (7581) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/p4_NCnnfK4/ea_profile.json
* 2024-11-17 02:13:34 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/p4_NCnnfK4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-17 02:13:34 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-18 02:13:01 (9491) [[32mINFO[0m] Self-update of script version 57 requested.
* 2024-11-18 02:13:02 (9513) [[32mINFO[0m] Script is up to date.
* 2024-11-18 02:13:03 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-18 02:13:03 (8440) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-18 02:13:03 (8441) [[32mINFO[0m] 
* 2024-11-18 02:13:05 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-18 02:13:05 (8441) [[32mINFO[0m] 
* 2024-11-18 02:13:05 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]         or
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]         compromise:
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-18 02:13:06 (8471) [[32mINFO[0m] 
* 2024-11-18 02:13:06 (5507) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-18 02:13:06 (5508) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-18 02:13:06 (8440) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-18 02:13:06 (8441) [[32mINFO[0m] 
* 2024-11-18 02:13:06 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-18 02:13:07 (8454) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-18 02:13:07 (8454) [[32mINFO[0m]               : epel extras updates
* 2024-11-18 02:13:07 (8454) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-18 02:13:07 (8454) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-18 02:13:07 (8471) [[32mINFO[0m] 
* 2024-11-18 02:13:07 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-18 02:13:07 (8441) [[32mINFO[0m] 
* 2024-11-18 02:13:07 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-18 02:13:07 (8454) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]         or
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]         compromise:
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m] 
* 2024-11-18 02:13:08 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-18 02:13:08 (8471) [[32mINFO[0m] 
* 2024-11-18 02:13:08 (5517) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-18 02:13:08 (5518) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-18 02:13:08 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-18 02:13:08 (7581) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5ws1nVkOw8/ea_profile.json
* 2024-11-18 02:13:10 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5ws1nVkOw8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-18 02:13:10 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-19 02:12:52 (9491) [[32mINFO[0m] Self-update of script version 57 requested.
* 2024-11-19 02:12:53 (9513) [[32mINFO[0m] Script is up to date.
* 2024-11-19 02:12:54 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-19 02:12:54 (8440) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-19 02:12:54 (8441) [[32mINFO[0m] 
* 2024-11-19 02:12:56 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-19 02:12:56 (8441) [[32mINFO[0m] 
* 2024-11-19 02:12:57 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-19 02:12:57 (8454) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]         or
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]         compromise:
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-19 02:12:58 (8471) [[32mINFO[0m] 
* 2024-11-19 02:12:58 (5507) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-19 02:12:58 (5508) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-19 02:12:58 (8440) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-19 02:12:58 (8441) [[32mINFO[0m] 
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m]               : epel extras updates
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-19 02:12:58 (8471) [[32mINFO[0m] 
* 2024-11-19 02:12:58 (8440) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-19 02:12:58 (8441) [[32mINFO[0m] 
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-19 02:12:58 (8454) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]         or
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]         compromise:
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m] 
* 2024-11-19 02:12:59 (8454) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-19 02:12:59 (8471) [[32mINFO[0m] 
* 2024-11-19 02:12:59 (5517) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-19 02:12:59 (5518) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-19 02:13:00 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-19 02:13:00 (7581) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/S3pF9BXp4b/ea_profile.json
* 2024-11-19 02:13:02 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/S3pF9BXp4b/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-19 02:13:02 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-20 02:12:10 (9491) [[32mINFO[0m] Self-update of script version 57 requested.
* 2024-11-20 02:12:10 (9496) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-11-20 02:12:12 (9505) [[32mINFO[0m] Script update to version 58 successful.
* 2024-11-20 02:12:13 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-20 02:12:13 (8444) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-20 02:12:13 (8445) [[32mINFO[0m] 
* 2024-11-20 02:12:17 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-20 02:12:17 (8445) [[32mINFO[0m] 
* 2024-11-20 02:12:17 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-20 02:12:17 (8458) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]         or
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]         compromise:
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-20 02:12:19 (8475) [[32mINFO[0m] 
* 2024-11-20 02:12:19 (5510) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-20 02:12:19 (5511) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-20 02:12:19 (8444) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-20 02:12:19 (8445) [[32mINFO[0m] 
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m]               : epel extras updates
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-20 02:12:19 (8475) [[32mINFO[0m] 
* 2024-11-20 02:12:19 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-20 02:12:19 (8445) [[32mINFO[0m] 
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-20 02:12:19 (8458) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]         or
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]         compromise:
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-20 02:12:21 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-20 02:12:21 (8475) [[32mINFO[0m] 
* 2024-11-20 02:12:21 (5520) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-20 02:12:21 (5521) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-20 02:12:22 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-20 02:12:22 (7585) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PIjtEL39II/ea_profile.json
* 2024-11-20 02:12:26 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PIjtEL39II/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-20 02:12:26 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-21 02:12:15 (9495) [[32mINFO[0m] Self-update of script version 58 requested.
* 2024-11-21 02:12:15 (9517) [[32mINFO[0m] Script is up to date.
* 2024-11-21 02:12:17 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-21 02:12:17 (8444) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-21 02:12:17 (8445) [[32mINFO[0m] 
* 2024-11-21 02:12:19 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-21 02:12:19 (8445) [[32mINFO[0m] 
* 2024-11-21 02:12:19 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-21 02:12:19 (8458) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]         or
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]         compromise:
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-21 02:12:20 (8475) [[32mINFO[0m] 
* 2024-11-21 02:12:20 (5510) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-21 02:12:20 (5511) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-21 02:12:20 (8444) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-21 02:12:20 (8445) [[32mINFO[0m] 
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m]               : epel extras updates
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-21 02:12:20 (8458) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-21 02:12:20 (8475) [[32mINFO[0m] 
* 2024-11-21 02:12:20 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-21 02:12:20 (8445) [[32mINFO[0m] 
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]         or
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]         compromise:
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-21 02:12:21 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-21 02:12:21 (8475) [[32mINFO[0m] 
* 2024-11-21 02:12:21 (5520) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:21 (5521) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-21 02:12:22 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-21 02:12:22 (7585) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oNFrjiyJaa/ea_profile.json
* 2024-11-21 02:12:25 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oNFrjiyJaa/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-21 02:12:25 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-22 02:12:15 (9495) [[32mINFO[0m] Self-update of script version 58 requested.
* 2024-11-22 02:12:15 (9517) [[32mINFO[0m] Script is up to date.
* 2024-11-22 02:12:17 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-22 02:12:17 (8444) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-22 02:12:17 (8445) [[32mINFO[0m] 
* 2024-11-22 02:12:19 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-22 02:12:19 (8445) [[32mINFO[0m] 
* 2024-11-22 02:12:20 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-22 02:12:20 (8458) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]         or
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]         compromise:
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-22 02:12:21 (8475) [[32mINFO[0m] 
* 2024-11-22 02:12:21 (5510) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-22 02:12:21 (5511) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-22 02:12:21 (8444) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-22 02:12:21 (8445) [[32mINFO[0m] 
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m]               : epel extras updates
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-22 02:12:21 (8475) [[32mINFO[0m] 
* 2024-11-22 02:12:21 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-22 02:12:21 (8445) [[32mINFO[0m] 
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-22 02:12:21 (8458) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]         or
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]         compromise:
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m] 
* 2024-11-22 02:12:23 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-22 02:12:23 (8475) [[32mINFO[0m] 
* 2024-11-22 02:12:23 (5520) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-22 02:12:23 (5521) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-22 02:12:23 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-22 02:12:23 (7585) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QpSPHQCpEi/ea_profile.json
* 2024-11-22 02:12:26 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QpSPHQCpEi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-22 02:12:26 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-22 15:46:13 (9495) [[32mINFO[0m] Self-update of script version 58 requested.
* 2024-11-22 15:46:13 (9517) [[32mINFO[0m] Script is up to date.
* 2024-11-22 15:46:15 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2024-11-22 15:46:15 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-22 15:46:15 (8444) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-22 15:46:15 (8445) [[32mINFO[0m] 
* 2024-11-22 15:46:17 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-22 15:46:17 (8445) [[32mINFO[0m] 
* 2024-11-22 15:46:17 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-22 15:46:17 (8458) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]         or
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]         compromise:
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:18 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-22 15:46:18 (8475) [[32mINFO[0m] 
* 2024-11-22 15:46:18 (5510) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-22 15:46:18 (5511) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-22 15:46:18 (8444) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-22 15:46:18 (8445) [[32mINFO[0m] 
* 2024-11-22 15:46:19 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-22 15:46:19 (8458) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-22 15:46:19 (8458) [[32mINFO[0m]               : epel extras updates
* 2024-11-22 15:46:19 (8458) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-22 15:46:19 (8458) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-22 15:46:19 (8475) [[32mINFO[0m] 
* 2024-11-22 15:46:19 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-22 15:46:19 (8445) [[32mINFO[0m] 
* 2024-11-22 15:46:19 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-22 15:46:19 (8458) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]         or
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]         compromise:
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m] 
* 2024-11-22 15:46:20 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-22 15:46:20 (8475) [[32mINFO[0m] 
* 2024-11-22 15:46:20 (5520) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-22 15:46:20 (5521) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-22 15:46:20 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-22 15:46:20 (7585) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ackot6teV0/ea_profile.json
* 2024-11-22 15:46:24 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ackot6teV0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-22 15:46:24 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-23 02:12:42 (9495) [[32mINFO[0m] Self-update of script version 58 requested.
* 2024-11-23 02:12:43 (9517) [[32mINFO[0m] Script is up to date.
* 2024-11-23 02:12:44 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-23 02:12:44 (8444) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-23 02:12:44 (8445) [[32mINFO[0m] 
* 2024-11-23 02:12:47 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-23 02:12:47 (8445) [[32mINFO[0m] 
* 2024-11-23 02:12:47 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-23 02:12:47 (8458) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]         or
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]         compromise:
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-23 02:12:49 (8475) [[32mINFO[0m] 
* 2024-11-23 02:12:49 (5510) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-23 02:12:49 (5511) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-23 02:12:49 (8444) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-23 02:12:49 (8445) [[32mINFO[0m] 
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m]               : epel extras updates
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-23 02:12:49 (8475) [[32mINFO[0m] 
* 2024-11-23 02:12:49 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-23 02:12:49 (8445) [[32mINFO[0m] 
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-23 02:12:49 (8458) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]         or
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]         compromise:
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m] 
* 2024-11-23 02:12:51 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-23 02:12:51 (8475) [[32mINFO[0m] 
* 2024-11-23 02:12:51 (5520) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-23 02:12:51 (5521) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-23 02:12:51 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-23 02:12:51 (7585) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/u46erSzOwt/ea_profile.json
* 2024-11-23 02:12:55 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/u46erSzOwt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-23 02:12:55 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-24 02:12:38 (9495) [[32mINFO[0m] Self-update of script version 58 requested.
* 2024-11-24 02:12:38 (9517) [[32mINFO[0m] Script is up to date.
* 2024-11-24 02:12:39 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-24 02:12:39 (8444) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-24 02:12:39 (8445) [[32mINFO[0m] 
* 2024-11-24 02:12:42 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-24 02:12:42 (8445) [[32mINFO[0m] 
* 2024-11-24 02:12:42 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-24 02:12:42 (8458) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]         or
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]         compromise:
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:43 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-24 02:12:43 (8475) [[32mINFO[0m] 
* 2024-11-24 02:12:43 (5510) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-24 02:12:43 (5511) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-24 02:12:43 (8444) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-24 02:12:43 (8445) [[32mINFO[0m] 
* 2024-11-24 02:12:44 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-24 02:12:44 (8458) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-24 02:12:44 (8458) [[32mINFO[0m]               : epel extras updates
* 2024-11-24 02:12:44 (8458) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-24 02:12:44 (8458) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-24 02:12:44 (8475) [[32mINFO[0m] 
* 2024-11-24 02:12:44 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-24 02:12:44 (8445) [[32mINFO[0m] 
* 2024-11-24 02:12:44 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-24 02:12:44 (8458) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]         or
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]         compromise:
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m] 
* 2024-11-24 02:12:45 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-24 02:12:45 (8475) [[32mINFO[0m] 
* 2024-11-24 02:12:45 (5520) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:45 (5521) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-24 02:12:45 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-24 02:12:45 (7585) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3WMFLvRyj9/ea_profile.json
* 2024-11-24 02:12:48 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3WMFLvRyj9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-24 02:12:48 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-25 02:12:15 (9495) [[32mINFO[0m] Self-update of script version 58 requested.
* 2024-11-25 02:12:15 (9517) [[32mINFO[0m] Script is up to date.
* 2024-11-25 02:12:17 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-25 02:12:17 (8444) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-25 02:12:17 (8445) [[32mINFO[0m] 
* 2024-11-25 02:12:19 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-25 02:12:19 (8445) [[32mINFO[0m] 
* 2024-11-25 02:12:19 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-25 02:12:19 (8458) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]         or
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]         compromise:
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-25 02:12:20 (8475) [[32mINFO[0m] 
* 2024-11-25 02:12:20 (5510) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-25 02:12:20 (5511) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-25 02:12:20 (8444) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-25 02:12:20 (8445) [[32mINFO[0m] 
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m]               : epel extras updates
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-25 02:12:20 (8458) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-25 02:12:20 (8475) [[32mINFO[0m] 
* 2024-11-25 02:12:20 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-25 02:12:20 (8445) [[32mINFO[0m] 
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]         or
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]         compromise:
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m] 
* 2024-11-25 02:12:21 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-25 02:12:21 (8475) [[32mINFO[0m] 
* 2024-11-25 02:12:21 (5520) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:21 (5521) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-25 02:12:22 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-25 02:12:22 (7585) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0yjIvkfYEd/ea_profile.json
* 2024-11-25 02:12:25 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0yjIvkfYEd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-25 02:12:25 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-26 02:12:15 (9495) [[32mINFO[0m] Self-update of script version 58 requested.
* 2024-11-26 02:12:15 (9517) [[32mINFO[0m] Script is up to date.
* 2024-11-26 02:12:17 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: 404 - 404 Not Found - HTTP ERROR	...propagated at /usr/local/cpanel/Cpanel/HttpRequest.pm line 531.
* 2024-11-26 02:12:17 (475) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 6214.
* 2024-11-26 02:12:17 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-27 02:14:50 (9495) [[32mINFO[0m] Self-update of script version 58 requested.
* 2024-11-27 02:14:50 (9517) [[32mINFO[0m] Script is up to date.
* 2024-11-27 02:14:51 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-27 02:14:51 (8444) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-27 02:14:51 (8445) [[32mINFO[0m] 
* 2024-11-27 02:14:55 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-27 02:14:55 (8445) [[32mINFO[0m] 
* 2024-11-27 02:14:55 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-27 02:14:55 (8458) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]         or
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]         compromise:
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-27 02:14:57 (8475) [[32mINFO[0m] 
* 2024-11-27 02:14:57 (5510) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-27 02:14:57 (5511) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-27 02:14:57 (8444) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-27 02:14:57 (8445) [[32mINFO[0m] 
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m]               : epel extras updates
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-27 02:14:57 (8475) [[32mINFO[0m] 
* 2024-11-27 02:14:57 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-27 02:14:57 (8445) [[32mINFO[0m] 
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-27 02:14:57 (8458) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]         or
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]         compromise:
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m] 
* 2024-11-27 02:14:59 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-27 02:14:59 (8475) [[32mINFO[0m] 
* 2024-11-27 02:14:59 (5520) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-27 02:14:59 (5521) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-27 02:14:59 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-27 02:14:59 (7585) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7kdfV0QiTb/ea_profile.json
* 2024-11-27 02:15:03 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7kdfV0QiTb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-27 02:15:03 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-28 02:12:32 (9495) [[32mINFO[0m] Self-update of script version 58 requested.
* 2024-11-28 02:12:32 (9517) [[32mINFO[0m] Script is up to date.
* 2024-11-28 02:12:34 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-28 02:12:34 (8444) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-28 02:12:34 (8445) [[32mINFO[0m] 
* 2024-11-28 02:12:37 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-28 02:12:37 (8445) [[32mINFO[0m] 
* 2024-11-28 02:12:37 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-28 02:12:37 (8458) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]         or
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]         compromise:
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-28 02:12:38 (8475) [[32mINFO[0m] 
* 2024-11-28 02:12:38 (5510) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-28 02:12:38 (5511) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-28 02:12:38 (8444) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-28 02:12:38 (8445) [[32mINFO[0m] 
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m]               : epel extras updates
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-28 02:12:38 (8458) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-28 02:12:38 (8475) [[32mINFO[0m] 
* 2024-11-28 02:12:38 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-28 02:12:38 (8445) [[32mINFO[0m] 
* 2024-11-28 02:12:39 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-28 02:12:39 (8458) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]         or
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]         compromise:
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m] 
* 2024-11-28 02:12:40 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-28 02:12:40 (8475) [[32mINFO[0m] 
* 2024-11-28 02:12:40 (5520) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-28 02:12:40 (5521) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-28 02:12:40 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-28 02:12:40 (7585) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4JzVpF3Zms/ea_profile.json
* 2024-11-28 02:12:44 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4JzVpF3Zms/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-28 02:12:44 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-29 02:12:15 (9495) [[32mINFO[0m] Self-update of script version 58 requested.
* 2024-11-29 02:12:15 (9517) [[32mINFO[0m] Script is up to date.
* 2024-11-29 02:12:17 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-29 02:12:17 (8444) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-29 02:12:17 (8445) [[32mINFO[0m] 
* 2024-11-29 02:12:19 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-29 02:12:19 (8445) [[32mINFO[0m] 
* 2024-11-29 02:12:19 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-29 02:12:19 (8458) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]         or
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]         compromise:
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:20 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-29 02:12:20 (8475) [[32mINFO[0m] 
* 2024-11-29 02:12:20 (5510) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-29 02:12:20 (5511) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-29 02:12:20 (8444) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-29 02:12:20 (8445) [[32mINFO[0m] 
* 2024-11-29 02:12:21 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-29 02:12:21 (8458) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-29 02:12:21 (8458) [[32mINFO[0m]               : epel extras updates
* 2024-11-29 02:12:21 (8458) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-29 02:12:21 (8458) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-29 02:12:21 (8475) [[32mINFO[0m] 
* 2024-11-29 02:12:21 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-29 02:12:21 (8445) [[32mINFO[0m] 
* 2024-11-29 02:12:21 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-29 02:12:21 (8458) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]         or
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]         compromise:
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m] 
* 2024-11-29 02:12:22 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-29 02:12:22 (8475) [[32mINFO[0m] 
* 2024-11-29 02:12:22 (5520) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:22 (5521) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-29 02:12:22 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-29 02:12:22 (7585) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ANRC13iDuz/ea_profile.json
* 2024-11-29 02:12:25 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ANRC13iDuz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-29 02:12:25 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-29 15:46:30 (9495) [[32mINFO[0m] Self-update of script version 58 requested.
* 2024-11-29 15:46:30 (9517) [[32mINFO[0m] Script is up to date.
* 2024-11-29 15:46:32 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-29 15:46:32 (8444) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-29 15:46:32 (8445) [[32mINFO[0m] 
* 2024-11-29 15:46:49 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-29 15:46:49 (8445) [[32mINFO[0m] 
* 2024-11-29 15:46:49 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-29 15:46:49 (8458) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]         or
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]         compromise:
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-29 15:46:52 (8475) [[32mINFO[0m] 
* 2024-11-29 15:46:52 (5510) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-29 15:46:52 (5511) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-29 15:46:52 (8444) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-29 15:46:52 (8445) [[32mINFO[0m] 
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m]               : epel extras updates
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-29 15:46:52 (8475) [[32mINFO[0m] 
* 2024-11-29 15:46:52 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-29 15:46:52 (8445) [[32mINFO[0m] 
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-29 15:46:52 (8458) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]         or
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]         compromise:
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m] 
* 2024-11-29 15:46:55 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-29 15:46:55 (8475) [[32mINFO[0m] 
* 2024-11-29 15:46:55 (5520) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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 15:46:55 (5521) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-29 15:46:55 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-29 15:46:55 (7585) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dLSe_p_Q8i/ea_profile.json
* 2024-11-29 15:47:01 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dLSe_p_Q8i/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-29 15:47:01 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-30 02:12:50 (9495) [[32mINFO[0m] Self-update of script version 58 requested.
* 2024-11-30 02:12:50 (9517) [[32mINFO[0m] Script is up to date.
* 2024-11-30 02:12:52 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-11-30 02:12:52 (8444) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-11-30 02:12:52 (8445) [[32mINFO[0m] 
* 2024-11-30 02:12:55 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-30 02:12:55 (8445) [[32mINFO[0m] 
* 2024-11-30 02:12:56 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-30 02:12:56 (8458) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] 
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] 
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] 
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] 
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] 
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] 
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] 
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]         or
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] 
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]         compromise:
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] 
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] 
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-30 02:12:58 (8475) [[32mINFO[0m] 
* 2024-11-30 02:12:58 (5510) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-30 02:12:58 (5511) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-11-30 02:12:58 (8444) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-11-30 02:12:58 (8445) [[32mINFO[0m] 
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m]               : epel extras updates
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-11-30 02:12:58 (8475) [[32mINFO[0m] 
* 2024-11-30 02:12:58 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-11-30 02:12:58 (8445) [[32mINFO[0m] 
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-30 02:12:58 (8458) [[32mINFO[0m] Determining fastest mirrors
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m] 
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m] 
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m] 
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m] 
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m] 
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m] 
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m] 
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]         or
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m] 
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]         compromise:
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m] 
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m] 
* 2024-11-30 02:13:00 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-30 02:13:00 (8475) [[32mINFO[0m] 
* 2024-11-30 02:13:00 (5520) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-30 02:13:00 (5521) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-11-30 02:13:01 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-30 02:13:01 (7585) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5uPRDqJ8Zc/ea_profile.json
* 2024-11-30 02:13:05 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5uPRDqJ8Zc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-30 02:13:05 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-01 02:12:44 (9495) [[32mINFO[0m] Self-update of script version 58 requested.
* 2024-12-01 02:12:44 (9517) [[32mINFO[0m] Script is up to date.
* 2024-12-01 02:12:46 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-01 02:12:46 (8444) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-01 02:12:46 (8445) [[32mINFO[0m] 
* 2024-12-01 02:12:48 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-01 02:12:48 (8445) [[32mINFO[0m] 
* 2024-12-01 02:12:48 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-01 02:12:48 (8458) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]         or
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]         compromise:
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-01 02:12:49 (8475) [[32mINFO[0m] 
* 2024-12-01 02:12:49 (5510) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-01 02:12:49 (5511) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-01 02:12:49 (8444) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-01 02:12:49 (8445) [[32mINFO[0m] 
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m]               : epel extras updates
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-01 02:12:49 (8475) [[32mINFO[0m] 
* 2024-12-01 02:12:49 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-01 02:12:49 (8445) [[32mINFO[0m] 
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-01 02:12:49 (8458) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]         or
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]         compromise:
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-01 02:12:50 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-01 02:12:50 (8475) [[32mINFO[0m] 
* 2024-12-01 02:12:50 (5520) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-01 02:12:50 (5521) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-01 02:12:50 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-01 02:12:50 (7585) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jbcm3PN0LH/ea_profile.json
* 2024-12-01 02:12:53 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jbcm3PN0LH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-12-01 02:12:53 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-02 02:12:31 (9495) [[32mINFO[0m] Self-update of script version 58 requested.
* 2024-12-02 02:12:31 (9517) [[32mINFO[0m] Script is up to date.
* 2024-12-02 02:12:33 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-02 02:12:33 (8444) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-02 02:12:33 (8445) [[32mINFO[0m] 
* 2024-12-02 02:12:35 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-02 02:12:35 (8445) [[32mINFO[0m] 
* 2024-12-02 02:12:35 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-02 02:12:35 (8458) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]         or
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]         compromise:
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:36 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-02 02:12:36 (8475) [[32mINFO[0m] 
* 2024-12-02 02:12:36 (5510) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-02 02:12:36 (5511) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-02 02:12:36 (8444) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-02 02:12:36 (8445) [[32mINFO[0m] 
* 2024-12-02 02:12:37 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-02 02:12:37 (8458) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-02 02:12:37 (8458) [[32mINFO[0m]               : epel extras updates
* 2024-12-02 02:12:37 (8458) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-02 02:12:37 (8458) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-02 02:12:37 (8475) [[32mINFO[0m] 
* 2024-12-02 02:12:37 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-02 02:12:37 (8445) [[32mINFO[0m] 
* 2024-12-02 02:12:37 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-02 02:12:37 (8458) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]         or
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]         compromise:
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m] 
* 2024-12-02 02:12:38 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-02 02:12:38 (8475) [[32mINFO[0m] 
* 2024-12-02 02:12:38 (5520) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-02 02:12:38 (5521) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-02 02:12:38 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-02 02:12:38 (7585) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rqq74zWuFg/ea_profile.json
* 2024-12-02 02:12:41 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rqq74zWuFg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-12-02 02:12:41 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-03 02:12:12 (9495) [[32mINFO[0m] Self-update of script version 58 requested.
* 2024-12-03 02:12:12 (9517) [[32mINFO[0m] Script is up to date.
* 2024-12-03 02:12:14 (3816) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-03 02:12:14 (8444) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-03 02:12:14 (8445) [[32mINFO[0m] 
* 2024-12-03 02:12:16 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-03 02:12:16 (8445) [[32mINFO[0m] 
* 2024-12-03 02:12:17 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-03 02:12:17 (8458) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/cPAddons-c7-x86_64-mirrorlist error was
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m] 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')
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]         or
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]         compromise:
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: cpanel-addons-production-feed/x86_64
* 2024-12-03 02:12:47 (8475) [[32mINFO[0m] 
* 2024-12-03 02:12:47 (5510) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://httpupdate.cpanel.net/cPAddons-c7-x86_64-mirrorlist error was
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')


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: cpanel-addons-production-feed/x86_64
* 2024-12-03 02:12:47 (5511) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-03 02:12:47 (8444) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-03 02:12:47 (8445) [[32mINFO[0m] 
* 2024-12-03 02:12:47 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-03 02:12:48 (8458) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-03 02:12:48 (8458) [[32mINFO[0m]               : epel extras updates
* 2024-12-03 02:12:48 (8458) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-03 02:12:48 (8458) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-03 02:12:48 (8475) [[32mINFO[0m] 
* 2024-12-03 02:12:48 (8444) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-03 02:12:48 (8445) [[32mINFO[0m] 
* 2024-12-03 02:12:48 (8458) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-03 02:12:48 (8458) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]         or
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]         compromise:
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m] 
* 2024-12-03 02:12:50 (8458) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-03 02:12:50 (8475) [[32mINFO[0m] 
* 2024-12-03 02:12:50 (5520) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-03 02:12:50 (5521) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-03 02:12:50 (1967) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-03 02:12:50 (7585) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WlwlSD1Sph/ea_profile.json
* 2024-12-03 02:12:55 (475) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WlwlSD1Sph/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-12-03 02:12:55 (439) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-04 02:13:27 (9495) [[32mINFO[0m] Self-update of script version 58 requested.
* 2024-12-04 02:13:27 (9500) [[32mINFO[0m] Newer version of script found. Downloading.
* 2024-12-04 02:13:28 (9509) [[32mINFO[0m] Script update to version 59 successful.
* 2024-12-04 02:13:33 (315) [[32mINFO[0m] Successfully verified signature for cpanel (key types: release).
* 2024-12-04 02:13:33 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-04 02:13:33 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-04 02:13:33 (9238) [[32mINFO[0m] 
* 2024-12-04 02:13:35 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-04 02:13:35 (9238) [[32mINFO[0m] 
* 2024-12-04 02:13:35 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-04 02:13:35 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]         or
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]         compromise:
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:36 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-04 02:13:36 (9268) [[32mINFO[0m] 
* 2024-12-04 02:13:36 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-04 02:13:36 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-04 02:13:36 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-04 02:13:36 (9238) [[32mINFO[0m] 
* 2024-12-04 02:13:37 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-04 02:13:37 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-04 02:13:37 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-04 02:13:37 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-04 02:13:37 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-04 02:13:37 (9268) [[32mINFO[0m] 
* 2024-12-04 02:13:37 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-04 02:13:37 (9238) [[32mINFO[0m] 
* 2024-12-04 02:13:37 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-04 02:13:37 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]         or
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]         compromise:
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m] 
* 2024-12-04 02:13:38 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-04 02:13:38 (9268) [[32mINFO[0m] 
* 2024-12-04 02:13:38 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-04 02:13:38 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-04 02:13:39 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-04 02:13:39 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/y0o4GkF8O2/ea_profile.json
* 2024-12-04 02:13:42 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/y0o4GkF8O2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-04 02:13:42 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-05 02:25:07 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-05 02:25:08 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-05 02:25:09 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: Failed to download signature at URL 'http://repo-ir.amazeservice.net/cpanelsync/TIERS.json.asc'.
* 2024-12-05 02:25:09 (484) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 6634.
* 2024-12-05 02:25:09 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-06 02:25:27 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-06 02:25:27 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-06 02:25:30 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: Failed to download signature at URL 'http://repo-ir.amazeservice.net/cpanelsync/TIERS.json.asc'.
* 2024-12-06 02:25:30 (484) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 6634.
* 2024-12-06 02:25:30 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-06 15:59:04 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-06 15:59:05 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-06 15:59:07 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: Failed to download signature at URL 'http://repo-ir.amazeservice.net/cpanelsync/TIERS.json.asc'.
* 2024-12-06 15:59:07 (484) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 6634.
* 2024-12-06 15:59:07 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-07 02:25:29 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-07 02:25:29 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-07 02:25:31 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: Failed to download signature at URL 'http://repo-ir.amazeservice.net/cpanelsync/TIERS.json.asc'.
* 2024-12-07 02:25:31 (484) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 6634.
* 2024-12-07 02:25:31 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-08 02:25:28 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-08 02:25:29 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-08 02:25:31 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: Failed to download signature at URL 'http://repo-ir.amazeservice.net/cpanelsync/TIERS.json.asc'.
* 2024-12-08 02:25:31 (484) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 6634.
* 2024-12-08 02:25:31 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-09 02:12:13 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-09 02:12:14 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-09 02:12:15 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-09 02:12:15 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-09 02:12:15 (9238) [[32mINFO[0m] 
* 2024-12-09 02:12:19 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-09 02:12:19 (9238) [[32mINFO[0m] 
* 2024-12-09 02:12:19 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-09 02:12:19 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]         or
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]         compromise:
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-09 02:12:21 (9268) [[32mINFO[0m] 
* 2024-12-09 02:12:21 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-09 02:12:21 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-09 02:12:21 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-09 02:12:21 (9238) [[32mINFO[0m] 
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-09 02:12:21 (9268) [[32mINFO[0m] 
* 2024-12-09 02:12:21 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-09 02:12:21 (9238) [[32mINFO[0m] 
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-09 02:12:21 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]         or
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]         compromise:
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m] 
* 2024-12-09 02:12:23 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-09 02:12:23 (9268) [[32mINFO[0m] 
* 2024-12-09 02:12:23 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:23 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-09 02:12:24 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-09 02:12:24 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GPIJn_pui4/ea_profile.json
* 2024-12-09 02:12:27 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GPIJn_pui4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-09 02:12:27 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-10 02:12:13 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-10 02:12:14 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-10 02:12:15 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-10 02:12:15 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-10 02:12:15 (9238) [[32mINFO[0m] 
* 2024-12-10 02:12:18 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-10 02:12:18 (9238) [[32mINFO[0m] 
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]         or
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]         compromise:
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:18 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-10 02:12:18 (9268) [[32mINFO[0m] 
* 2024-12-10 02:12:18 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-10 02:12:18 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-10 02:12:18 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-10 02:12:18 (9238) [[32mINFO[0m] 
* 2024-12-10 02:12:19 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-10 02:12:19 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-10 02:12:19 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-10 02:12:19 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-10 02:12:19 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-10 02:12:19 (9268) [[32mINFO[0m] 
* 2024-12-10 02:12:19 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-10 02:12:19 (9238) [[32mINFO[0m] 
* 2024-12-10 02:12:19 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-10 02:12:19 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]         or
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]         compromise:
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-10 02:12:20 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-10 02:12:20 (9268) [[32mINFO[0m] 
* 2024-12-10 02:12:20 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:20 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-10 02:12:20 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-10 02:12:20 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/g3zkvIXTz6/ea_profile.json
* 2024-12-10 02:12:23 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/g3zkvIXTz6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-10 02:12:23 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-11 02:12:09 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-11 02:12:10 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-11 02:12:11 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-11 02:12:11 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-11 02:12:11 (9238) [[32mINFO[0m] 
* 2024-12-11 02:12:14 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-11 02:12:14 (9238) [[32mINFO[0m] 
* 2024-12-11 02:12:14 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-11 02:12:14 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]         or
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]         compromise:
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-11 02:12:15 (9268) [[32mINFO[0m] 
* 2024-12-11 02:12:15 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-11 02:12:15 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-11 02:12:15 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-11 02:12:15 (9238) [[32mINFO[0m] 
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-11 02:12:15 (9268) [[32mINFO[0m] 
* 2024-12-11 02:12:15 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-11 02:12:15 (9238) [[32mINFO[0m] 
* 2024-12-11 02:12:15 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-11 02:12:16 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]         or
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]         compromise:
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-11 02:12:17 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-11 02:12:17 (9268) [[32mINFO[0m] 
* 2024-12-11 02:12:17 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:17 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-11 02:12:17 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-11 02:12:17 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vLI0qaAakk/ea_profile.json
* 2024-12-11 02:12:20 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vLI0qaAakk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-11 02:12:20 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-12 02:14:04 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-12 02:14:04 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-12 02:14:06 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-12 02:14:06 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-12 02:14:06 (9238) [[32mINFO[0m] 
* 2024-12-12 02:14:09 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-12 02:14:09 (9238) [[32mINFO[0m] 
* 2024-12-12 02:14:09 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-12 02:14:09 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]         or
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]         compromise:
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-12 02:14:11 (9268) [[32mINFO[0m] 
* 2024-12-12 02:14:11 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-12 02:14:11 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-12 02:14:11 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-12 02:14:11 (9238) [[32mINFO[0m] 
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-12 02:14:11 (9268) [[32mINFO[0m] 
* 2024-12-12 02:14:11 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-12 02:14:11 (9238) [[32mINFO[0m] 
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-12 02:14:11 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]         or
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]         compromise:
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m] 
* 2024-12-12 02:14:13 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-12 02:14:13 (9268) [[32mINFO[0m] 
* 2024-12-12 02:14:13 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:14:13 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-12 02:14:13 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-12 02:14:13 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FXPMf96i2i/ea_profile.json
* 2024-12-12 02:14:17 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FXPMf96i2i/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-12 02:14:17 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-13 02:12:15 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-13 02:12:15 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-13 02:12:17 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-13 02:12:17 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-13 02:12:17 (9238) [[32mINFO[0m] 
* 2024-12-13 02:12:19 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-13 02:12:19 (9238) [[32mINFO[0m] 
* 2024-12-13 02:12:19 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-13 02:12:19 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]         or
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]         compromise:
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-13 02:12:20 (9268) [[32mINFO[0m] 
* 2024-12-13 02:12:20 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-13 02:12:20 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-13 02:12:20 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-13 02:12:20 (9238) [[32mINFO[0m] 
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-13 02:12:20 (9268) [[32mINFO[0m] 
* 2024-12-13 02:12:20 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-13 02:12:20 (9238) [[32mINFO[0m] 
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-13 02:12:20 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]         or
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]         compromise:
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-13 02:12:21 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-13 02:12:21 (9268) [[32mINFO[0m] 
* 2024-12-13 02:12:21 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-13 02:12:21 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-13 02:12:22 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-13 02:12:22 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ONriE_t1sV/ea_profile.json
* 2024-12-13 02:12:25 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ONriE_t1sV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-13 02:12:25 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-13 15:46:33 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-13 15:46:33 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-13 15:46:35 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-13 15:46:35 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-13 15:46:35 (9238) [[32mINFO[0m] 
* 2024-12-13 15:46:36 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-13 15:46:36 (9238) [[32mINFO[0m] 
* 2024-12-13 15:46:37 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-13 15:46:37 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]         or
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]         compromise:
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-13 15:46:39 (9268) [[32mINFO[0m] 
* 2024-12-13 15:46:39 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-13 15:46:39 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-13 15:46:39 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-13 15:46:39 (9238) [[32mINFO[0m] 
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-13 15:46:39 (9268) [[32mINFO[0m] 
* 2024-12-13 15:46:39 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-13 15:46:39 (9238) [[32mINFO[0m] 
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-13 15:46:39 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]         or
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]         compromise:
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m] 
* 2024-12-13 15:46:42 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-13 15:46:42 (9268) [[32mINFO[0m] 
* 2024-12-13 15:46:42 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-13 15:46:42 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-13 15:46:42 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-13 15:46:42 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3K0fbfQI5w/ea_profile.json
* 2024-12-13 15:46:46 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3K0fbfQI5w/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-13 15:46:46 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-14 02:12:37 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-14 02:12:37 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-14 02:12:39 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-14 02:12:39 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-14 02:12:39 (9238) [[32mINFO[0m] 
* 2024-12-14 02:12:42 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-14 02:12:42 (9238) [[32mINFO[0m] 
* 2024-12-14 02:12:42 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-14 02:12:42 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]         or
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]         compromise:
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-14 02:12:43 (9268) [[32mINFO[0m] 
* 2024-12-14 02:12:43 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-14 02:12:43 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-14 02:12:43 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-14 02:12:43 (9238) [[32mINFO[0m] 
* 2024-12-14 02:12:43 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-14 02:12:44 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-14 02:12:44 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-14 02:12:44 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-14 02:12:44 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-14 02:12:44 (9268) [[32mINFO[0m] 
* 2024-12-14 02:12:44 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-14 02:12:44 (9238) [[32mINFO[0m] 
* 2024-12-14 02:12:44 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-14 02:12:44 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]         or
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]         compromise:
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-14 02:12:45 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-14 02:12:45 (9268) [[32mINFO[0m] 
* 2024-12-14 02:12:45 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-14 02:12:45 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-14 02:12:46 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-14 02:12:46 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6d3esgbuOv/ea_profile.json
* 2024-12-14 02:12:49 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6d3esgbuOv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-14 02:12:49 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-15 02:12:56 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-15 02:12:56 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-15 02:12:58 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-15 02:12:58 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-15 02:12:58 (9238) [[32mINFO[0m] 
* 2024-12-15 02:13:00 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-15 02:13:00 (9238) [[32mINFO[0m] 
* 2024-12-15 02:13:00 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-15 02:13:00 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]         or
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]         compromise:
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-15 02:13:01 (9268) [[32mINFO[0m] 
* 2024-12-15 02:13:01 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-15 02:13:01 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-15 02:13:01 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-15 02:13:01 (9238) [[32mINFO[0m] 
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-15 02:13:01 (9268) [[32mINFO[0m] 
* 2024-12-15 02:13:01 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-15 02:13:01 (9238) [[32mINFO[0m] 
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-15 02:13:01 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]         or
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]         compromise:
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m] 
* 2024-12-15 02:13:02 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-15 02:13:02 (9268) [[32mINFO[0m] 
* 2024-12-15 02:13:02 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:13:02 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-15 02:13:02 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-15 02:13:02 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tMPMLETR7N/ea_profile.json
* 2024-12-15 02:13:05 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tMPMLETR7N/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-15 02:13:05 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-16 02:12:31 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-16 02:12:32 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-16 02:12:33 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-16 02:12:33 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-16 02:12:33 (9238) [[32mINFO[0m] 
* 2024-12-16 02:12:35 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-16 02:12:35 (9238) [[32mINFO[0m] 
* 2024-12-16 02:12:35 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-16 02:12:35 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]         or
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]         compromise:
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-16 02:12:36 (9268) [[32mINFO[0m] 
* 2024-12-16 02:12:36 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-16 02:12:36 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-16 02:12:36 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-16 02:12:36 (9238) [[32mINFO[0m] 
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-16 02:12:36 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-16 02:12:36 (9268) [[32mINFO[0m] 
* 2024-12-16 02:12:36 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-16 02:12:36 (9238) [[32mINFO[0m] 
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]         or
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]         compromise:
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m] 
* 2024-12-16 02:12:37 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-16 02:12:37 (9268) [[32mINFO[0m] 
* 2024-12-16 02:12:37 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:37 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-16 02:12:37 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-16 02:12:37 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QqS7mQuwYo/ea_profile.json
* 2024-12-16 02:12:40 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QqS7mQuwYo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-16 02:12:40 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-17 02:12:32 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-17 02:12:33 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-17 02:12:34 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-17 02:12:34 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-17 02:12:34 (9238) [[32mINFO[0m] 
* 2024-12-17 02:12:39 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-17 02:12:39 (9238) [[32mINFO[0m] 
* 2024-12-17 02:12:39 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-17 02:12:39 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]         or
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]         compromise:
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-17 02:12:42 (9268) [[32mINFO[0m] 
* 2024-12-17 02:12:42 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-17 02:12:42 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-17 02:12:42 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-17 02:12:42 (9238) [[32mINFO[0m] 
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-17 02:12:42 (9268) [[32mINFO[0m] 
* 2024-12-17 02:12:42 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-17 02:12:42 (9238) [[32mINFO[0m] 
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-17 02:12:42 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]         or
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]         compromise:
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m] 
* 2024-12-17 02:12:46 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-17 02:12:46 (9268) [[32mINFO[0m] 
* 2024-12-17 02:12:46 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:46 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-17 02:12:46 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-17 02:12:46 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/W_Atl4w_mt/ea_profile.json
* 2024-12-17 02:12:51 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/W_Atl4w_mt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-17 02:12:51 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-17 09:05:49 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-17 09:05:50 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-17 09:05:51 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-17 09:05:51 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-17 09:05:51 (9238) [[32mINFO[0m] 
* 2024-12-17 09:05:54 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-17 09:05:54 (9238) [[32mINFO[0m] 
* 2024-12-17 09:05:54 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-17 09:05:54 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]         or
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]         compromise:
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-17 09:05:55 (9268) [[32mINFO[0m] 
* 2024-12-17 09:05:55 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-17 09:05:55 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-17 09:05:55 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-17 09:05:55 (9238) [[32mINFO[0m] 
* 2024-12-17 09:05:55 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-17 09:05:56 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-17 09:05:56 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-17 09:05:56 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-17 09:05:56 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-17 09:05:56 (9268) [[32mINFO[0m] 
* 2024-12-17 09:05:56 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-17 09:05:56 (9238) [[32mINFO[0m] 
* 2024-12-17 09:05:56 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-17 09:05:56 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]         or
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]         compromise:
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m] 
* 2024-12-17 09:05:57 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-17 09:05:57 (9268) [[32mINFO[0m] 
* 2024-12-17 09:05:57 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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 09:05:57 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-17 09:05:57 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-17 09:05:57 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RxTAvSmE7L/ea_profile.json
* 2024-12-17 09:06:01 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RxTAvSmE7L/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-17 09:06:01 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-18 02:12:35 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-18 02:12:36 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-18 02:12:37 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-18 02:12:37 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-18 02:12:37 (9238) [[32mINFO[0m] 
* 2024-12-18 02:12:41 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-18 02:12:41 (9238) [[32mINFO[0m] 
* 2024-12-18 02:12:41 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-18 02:12:41 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]         or
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]         compromise:
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-18 02:12:44 (9268) [[32mINFO[0m] 
* 2024-12-18 02:12:44 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-18 02:12:44 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-18 02:12:44 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-18 02:12:44 (9238) [[32mINFO[0m] 
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-18 02:12:44 (9268) [[32mINFO[0m] 
* 2024-12-18 02:12:44 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-18 02:12:44 (9238) [[32mINFO[0m] 
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-18 02:12:44 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]         or
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]         compromise:
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m] 
* 2024-12-18 02:12:47 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-18 02:12:47 (9268) [[32mINFO[0m] 
* 2024-12-18 02:12:47 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:47 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-18 02:12:47 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-18 02:12:47 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZGYPLvsTRz/ea_profile.json
* 2024-12-18 02:12:51 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZGYPLvsTRz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-18 02:12:51 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-19 02:12:12 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-19 02:12:13 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-19 02:12:14 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-19 02:12:14 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-19 02:12:14 (9238) [[32mINFO[0m] 
* 2024-12-19 02:12:16 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-19 02:12:16 (9238) [[32mINFO[0m] 
* 2024-12-19 02:12:17 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-19 02:12:17 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]         or
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]         compromise:
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-19 02:12:18 (9268) [[32mINFO[0m] 
* 2024-12-19 02:12:18 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-19 02:12:18 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-19 02:12:18 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-19 02:12:18 (9238) [[32mINFO[0m] 
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-19 02:12:18 (9268) [[32mINFO[0m] 
* 2024-12-19 02:12:18 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-19 02:12:18 (9238) [[32mINFO[0m] 
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-19 02:12:18 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]         or
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]         compromise:
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-19 02:12:19 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-19 02:12:19 (9268) [[32mINFO[0m] 
* 2024-12-19 02:12:19 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:19 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-19 02:12:19 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-19 02:12:19 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Hf5Z9tonvo/ea_profile.json
* 2024-12-19 02:12:22 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Hf5Z9tonvo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-19 02:12:22 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-20 02:12:12 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-20 02:12:13 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-20 02:12:14 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-20 02:12:14 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-20 02:12:14 (9238) [[32mINFO[0m] 
* 2024-12-20 02:12:17 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-20 02:12:17 (9238) [[32mINFO[0m] 
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]         or
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]         compromise:
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-20 02:12:17 (9268) [[32mINFO[0m] 
* 2024-12-20 02:12:17 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-20 02:12:17 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-20 02:12:17 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-20 02:12:17 (9238) [[32mINFO[0m] 
* 2024-12-20 02:12:17 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-20 02:12:18 (9268) [[32mINFO[0m] 
* 2024-12-20 02:12:18 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-20 02:12:18 (9238) [[32mINFO[0m] 
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]         or
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]         compromise:
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-20 02:12:18 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-20 02:12:18 (9268) [[32mINFO[0m] 
* 2024-12-20 02:12:18 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-20 02:12:18 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-20 02:12:19 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-20 02:12:19 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8yQ1n7wuPl/ea_profile.json
* 2024-12-20 02:12:21 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8yQ1n7wuPl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-20 02:12:21 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-20 15:46:10 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-20 15:46:10 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-20 15:46:12 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-20 15:46:12 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-20 15:46:12 (9238) [[32mINFO[0m] 
* 2024-12-20 15:46:14 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-20 15:46:14 (9238) [[32mINFO[0m] 
* 2024-12-20 15:46:14 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-20 15:46:14 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]         or
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]         compromise:
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-20 15:46:15 (9268) [[32mINFO[0m] 
* 2024-12-20 15:46:15 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-20 15:46:15 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-20 15:46:15 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-20 15:46:15 (9238) [[32mINFO[0m] 
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-20 15:46:15 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-20 15:46:15 (9268) [[32mINFO[0m] 
* 2024-12-20 15:46:15 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-20 15:46:15 (9238) [[32mINFO[0m] 
* 2024-12-20 15:46:16 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-20 15:46:16 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]         or
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]         compromise:
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m] 
* 2024-12-20 15:46:17 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-20 15:46:17 (9268) [[32mINFO[0m] 
* 2024-12-20 15:46:17 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-20 15:46:17 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-20 15:46:17 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-20 15:46:17 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YjnItHJpeq/ea_profile.json
* 2024-12-20 15:46:20 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YjnItHJpeq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-20 15:46:20 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-21 02:12:59 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-21 02:13:00 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-21 02:13:01 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-21 02:13:01 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-21 02:13:01 (9238) [[32mINFO[0m] 
* 2024-12-21 02:13:03 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-21 02:13:03 (9238) [[32mINFO[0m] 
* 2024-12-21 02:13:03 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-21 02:13:03 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]         or
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]         compromise:
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-21 02:13:04 (9268) [[32mINFO[0m] 
* 2024-12-21 02:13:04 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-21 02:13:04 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-21 02:13:04 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-21 02:13:04 (9238) [[32mINFO[0m] 
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-21 02:13:04 (9268) [[32mINFO[0m] 
* 2024-12-21 02:13:04 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-21 02:13:04 (9238) [[32mINFO[0m] 
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-21 02:13:04 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]         or
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]         compromise:
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m] 
* 2024-12-21 02:13:05 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-21 02:13:05 (9268) [[32mINFO[0m] 
* 2024-12-21 02:13:05 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-21 02:13:05 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-21 02:13:05 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-21 02:13:05 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/67mGdSguN3/ea_profile.json
* 2024-12-21 02:13:09 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/67mGdSguN3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-21 02:13:09 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-22 02:13:16 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-22 02:13:16 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-22 02:13:18 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-22 02:13:18 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-22 02:13:18 (9238) [[32mINFO[0m] 
* 2024-12-22 02:13:21 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-22 02:13:21 (9238) [[32mINFO[0m] 
* 2024-12-22 02:13:21 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-22 02:13:21 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]         or
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]         compromise:
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-22 02:13:22 (9268) [[32mINFO[0m] 
* 2024-12-22 02:13:22 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-22 02:13:22 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-22 02:13:22 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-22 02:13:22 (9238) [[32mINFO[0m] 
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-22 02:13:22 (9268) [[32mINFO[0m] 
* 2024-12-22 02:13:22 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-22 02:13:22 (9238) [[32mINFO[0m] 
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-22 02:13:22 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]         or
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]         compromise:
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m] 
* 2024-12-22 02:13:23 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-22 02:13:23 (9268) [[32mINFO[0m] 
* 2024-12-22 02:13:23 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-22 02:13:23 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-22 02:13:23 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-22 02:13:23 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CPqNx2SyWU/ea_profile.json
* 2024-12-22 02:13:25 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CPqNx2SyWU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-22 02:13:25 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-23 02:12:10 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-23 02:12:10 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-23 02:12:11 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-23 02:12:11 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-23 02:12:11 (9238) [[32mINFO[0m] 
* 2024-12-23 02:12:14 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-23 02:12:14 (9238) [[32mINFO[0m] 
* 2024-12-23 02:12:14 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-23 02:12:14 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]         or
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]         compromise:
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-23 02:12:16 (9268) [[32mINFO[0m] 
* 2024-12-23 02:12:16 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-23 02:12:16 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-23 02:12:16 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-23 02:12:16 (9238) [[32mINFO[0m] 
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-23 02:12:16 (9268) [[32mINFO[0m] 
* 2024-12-23 02:12:16 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-23 02:12:16 (9238) [[32mINFO[0m] 
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-23 02:12:16 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]         or
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]         compromise:
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-23 02:12:18 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-23 02:12:18 (9268) [[32mINFO[0m] 
* 2024-12-23 02:12:18 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:18 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-23 02:12:18 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-23 02:12:18 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YJsGeX4hPE/ea_profile.json
* 2024-12-23 02:12:21 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YJsGeX4hPE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-23 02:12:21 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-24 02:12:10 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-24 02:12:11 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-24 02:12:12 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-24 02:12:12 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-24 02:12:12 (9238) [[32mINFO[0m] 
* 2024-12-24 02:12:16 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-24 02:12:16 (9238) [[32mINFO[0m] 
* 2024-12-24 02:12:16 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-24 02:12:16 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]         or
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]         compromise:
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-24 02:12:19 (9268) [[32mINFO[0m] 
* 2024-12-24 02:12:19 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-24 02:12:19 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-24 02:12:19 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-24 02:12:19 (9238) [[32mINFO[0m] 
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-24 02:12:19 (9268) [[32mINFO[0m] 
* 2024-12-24 02:12:19 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-24 02:12:19 (9238) [[32mINFO[0m] 
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-24 02:12:19 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]         or
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]         compromise:
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m] 
* 2024-12-24 02:12:21 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-24 02:12:21 (9268) [[32mINFO[0m] 
* 2024-12-24 02:12:21 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-24 02:12:21 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-24 02:12:22 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-24 02:12:22 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PvBc73p41r/ea_profile.json
* 2024-12-24 02:12:26 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PvBc73p41r/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-24 02:12:26 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-25 02:13:16 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-25 02:13:16 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-25 02:13:18 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-25 02:13:18 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-25 02:13:18 (9238) [[32mINFO[0m] 
* 2024-12-25 02:13:20 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-25 02:13:20 (9238) [[32mINFO[0m] 
* 2024-12-25 02:13:20 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-25 02:13:20 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]         or
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]         compromise:
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-25 02:13:21 (9268) [[32mINFO[0m] 
* 2024-12-25 02:13:21 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-25 02:13:21 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-25 02:13:21 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-25 02:13:21 (9238) [[32mINFO[0m] 
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-25 02:13:21 (9268) [[32mINFO[0m] 
* 2024-12-25 02:13:21 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-25 02:13:21 (9238) [[32mINFO[0m] 
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-25 02:13:21 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]         or
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]         compromise:
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m] 
* 2024-12-25 02:13:22 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-25 02:13:22 (9268) [[32mINFO[0m] 
* 2024-12-25 02:13:22 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-25 02:13:22 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-25 02:13:22 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-25 02:13:22 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RPyOcA8IbK/ea_profile.json
* 2024-12-25 02:13:25 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RPyOcA8IbK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-25 02:13:25 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-26 02:12:12 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-26 02:12:12 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-26 02:12:14 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-26 02:12:14 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-26 02:12:14 (9238) [[32mINFO[0m] 
* 2024-12-26 02:12:17 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-26 02:12:17 (9238) [[32mINFO[0m] 
* 2024-12-26 02:12:17 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-26 02:12:17 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]         or
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]         compromise:
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-26 02:12:19 (9268) [[32mINFO[0m] 
* 2024-12-26 02:12:19 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-26 02:12:19 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-26 02:12:19 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-26 02:12:19 (9238) [[32mINFO[0m] 
* 2024-12-26 02:12:19 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-26 02:12:20 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-26 02:12:20 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-26 02:12:20 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-26 02:12:20 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-26 02:12:20 (9268) [[32mINFO[0m] 
* 2024-12-26 02:12:20 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-26 02:12:20 (9238) [[32mINFO[0m] 
* 2024-12-26 02:12:20 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-26 02:12:20 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]         or
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]         compromise:
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m] 
* 2024-12-26 02:12:22 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-26 02:12:22 (9268) [[32mINFO[0m] 
* 2024-12-26 02:12:22 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:22 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-26 02:12:22 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-26 02:12:22 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3KH6Xln_4K/ea_profile.json
* 2024-12-26 02:12:26 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3KH6Xln_4K/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-26 02:12:26 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-27 02:12:10 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-27 02:12:10 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-27 02:12:12 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-27 02:12:12 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-27 02:12:12 (9238) [[32mINFO[0m] 
* 2024-12-27 02:12:14 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-27 02:12:14 (9238) [[32mINFO[0m] 
* 2024-12-27 02:12:15 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-27 02:12:15 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]         or
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]         compromise:
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-27 02:12:16 (9268) [[32mINFO[0m] 
* 2024-12-27 02:12:16 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-27 02:12:16 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-27 02:12:16 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-27 02:12:16 (9238) [[32mINFO[0m] 
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-27 02:12:16 (9268) [[32mINFO[0m] 
* 2024-12-27 02:12:16 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-27 02:12:16 (9238) [[32mINFO[0m] 
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-27 02:12:16 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]         or
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]         compromise:
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m] 
* 2024-12-27 02:12:18 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-27 02:12:18 (9268) [[32mINFO[0m] 
* 2024-12-27 02:12:18 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-27 02:12:18 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-27 02:12:18 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-27 02:12:18 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1_9dr68P2B/ea_profile.json
* 2024-12-27 02:12:22 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1_9dr68P2B/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-27 02:12:22 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-27 15:46:15 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-27 15:46:16 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-27 15:46:17 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-27 15:46:17 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-27 15:46:17 (9238) [[32mINFO[0m] 
* 2024-12-27 15:46:21 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-27 15:46:21 (9238) [[32mINFO[0m] 
* 2024-12-27 15:46:21 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-27 15:46:21 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]         or
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]         compromise:
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-27 15:46:23 (9268) [[32mINFO[0m] 
* 2024-12-27 15:46:23 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-27 15:46:23 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-27 15:46:23 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-27 15:46:23 (9238) [[32mINFO[0m] 
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-27 15:46:23 (9268) [[32mINFO[0m] 
* 2024-12-27 15:46:23 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-27 15:46:23 (9238) [[32mINFO[0m] 
* 2024-12-27 15:46:23 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-27 15:46:24 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]         or
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]         compromise:
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m] 
* 2024-12-27 15:46:26 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-27 15:46:26 (9268) [[32mINFO[0m] 
* 2024-12-27 15:46:26 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-27 15:46:26 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-27 15:46:26 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-27 15:46:26 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yi150xov43/ea_profile.json
* 2024-12-27 15:46:30 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yi150xov43/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-27 15:46:30 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-28 02:12:36 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-28 02:12:37 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-28 02:12:38 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-28 02:12:38 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-28 02:12:38 (9238) [[32mINFO[0m] 
* 2024-12-28 02:12:42 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-28 02:12:42 (9238) [[32mINFO[0m] 
* 2024-12-28 02:12:42 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-28 02:12:42 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]         or
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]         compromise:
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-28 02:12:44 (9268) [[32mINFO[0m] 
* 2024-12-28 02:12:44 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-28 02:12:44 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-28 02:12:44 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-28 02:12:44 (9238) [[32mINFO[0m] 
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-28 02:12:44 (9268) [[32mINFO[0m] 
* 2024-12-28 02:12:44 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-28 02:12:44 (9238) [[32mINFO[0m] 
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-28 02:12:44 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]         or
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]         compromise:
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m] 
* 2024-12-28 02:12:48 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-28 02:12:48 (9268) [[32mINFO[0m] 
* 2024-12-28 02:12:48 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:48 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-28 02:12:48 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-28 02:12:48 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UGMqogjmAo/ea_profile.json
* 2024-12-28 02:12:53 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UGMqogjmAo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-28 02:12:53 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-29 02:12:38 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-29 02:12:38 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-29 02:12:40 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-29 02:12:40 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-29 02:12:40 (9238) [[32mINFO[0m] 
* 2024-12-29 02:12:42 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-29 02:12:42 (9238) [[32mINFO[0m] 
* 2024-12-29 02:12:42 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-29 02:12:42 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]         or
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]         compromise:
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-29 02:12:43 (9268) [[32mINFO[0m] 
* 2024-12-29 02:12:43 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-29 02:12:43 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-29 02:12:43 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-29 02:12:43 (9238) [[32mINFO[0m] 
* 2024-12-29 02:12:43 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-29 02:12:44 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-29 02:12:44 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-29 02:12:44 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-29 02:12:44 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-29 02:12:44 (9268) [[32mINFO[0m] 
* 2024-12-29 02:12:44 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-29 02:12:44 (9238) [[32mINFO[0m] 
* 2024-12-29 02:12:44 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-29 02:12:44 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]         or
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]         compromise:
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m] 
* 2024-12-29 02:12:45 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-29 02:12:45 (9268) [[32mINFO[0m] 
* 2024-12-29 02:12:45 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:45 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-29 02:12:45 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-29 02:12:45 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/r7Kce9e6gi/ea_profile.json
* 2024-12-29 02:12:48 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/r7Kce9e6gi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-29 02:12:48 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-30 02:12:45 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-30 02:12:46 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-30 02:12:47 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-30 02:12:47 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-30 02:12:47 (9238) [[32mINFO[0m] 
* 2024-12-30 02:12:53 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-30 02:12:53 (9238) [[32mINFO[0m] 
* 2024-12-30 02:12:53 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-30 02:12:53 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m] 
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m] 
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m] 
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m] 
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m] 
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m] 
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m] 
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]         or
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m] 
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]         compromise:
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m] 
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m] 
* 2024-12-30 02:12:56 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-30 02:12:57 (9268) [[32mINFO[0m] 
* 2024-12-30 02:12:57 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-30 02:12:57 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-30 02:12:57 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-30 02:12:57 (9238) [[32mINFO[0m] 
* 2024-12-30 02:12:57 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-30 02:12:57 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-30 02:12:57 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-30 02:12:57 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-30 02:12:57 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-30 02:12:57 (9268) [[32mINFO[0m] 
* 2024-12-30 02:12:57 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-30 02:12:57 (9238) [[32mINFO[0m] 
* 2024-12-30 02:12:57 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-30 02:12:57 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m] 
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m] 
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m] 
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m] 
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m] 
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m] 
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m] 
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]         or
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m] 
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]         compromise:
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m] 
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m] 
* 2024-12-30 02:13:00 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-30 02:13:00 (9268) [[32mINFO[0m] 
* 2024-12-30 02:13:00 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-30 02:13:00 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-30 02:13:01 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-30 02:13:01 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Nf1Jli1JDv/ea_profile.json
* 2024-12-30 02:13:06 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Nf1Jli1JDv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-30 02:13:06 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-31 02:12:42 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2024-12-31 02:12:43 (10313) [[32mINFO[0m] Script is up to date.
* 2024-12-31 02:12:44 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2024-12-31 02:12:44 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2024-12-31 02:12:44 (9238) [[32mINFO[0m] 
* 2024-12-31 02:12:47 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-31 02:12:47 (9238) [[32mINFO[0m] 
* 2024-12-31 02:12:47 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-31 02:12:47 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]         or
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]         compromise:
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-31 02:12:49 (9268) [[32mINFO[0m] 
* 2024-12-31 02:12:49 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-31 02:12:49 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2024-12-31 02:12:49 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2024-12-31 02:12:49 (9238) [[32mINFO[0m] 
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m]               : epel extras updates
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2024-12-31 02:12:49 (9268) [[32mINFO[0m] 
* 2024-12-31 02:12:49 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2024-12-31 02:12:49 (9238) [[32mINFO[0m] 
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-31 02:12:49 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]         or
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]         compromise:
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m] 
* 2024-12-31 02:12:51 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-31 02:12:51 (9268) [[32mINFO[0m] 
* 2024-12-31 02:12:51 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-31 02:12:51 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2024-12-31 02:12:51 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-31 02:12:51 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/80ZRKbtR3e/ea_profile.json
* 2024-12-31 02:12:55 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/80ZRKbtR3e/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-31 02:12:55 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-01 02:12:12 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-01 02:12:13 (10313) [[32mINFO[0m] Script is up to date.
* 2025-01-01 02:12:14 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-01 02:12:14 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-01 02:12:14 (9238) [[32mINFO[0m] 
* 2025-01-01 02:12:16 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-01 02:12:16 (9238) [[32mINFO[0m] 
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]         or
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]         compromise:
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-01 02:12:17 (9268) [[32mINFO[0m] 
* 2025-01-01 02:12:17 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-01 02:12:17 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-01 02:12:17 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-01 02:12:17 (9238) [[32mINFO[0m] 
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m]               : epel extras updates
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-01 02:12:17 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-01 02:12:17 (9268) [[32mINFO[0m] 
* 2025-01-01 02:12:17 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-01 02:12:17 (9238) [[32mINFO[0m] 
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]         or
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]         compromise:
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m] 
* 2025-01-01 02:12:18 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-01 02:12:18 (9268) [[32mINFO[0m] 
* 2025-01-01 02:12:18 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:18 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-01 02:12:18 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-01 02:12:18 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sAHYQnsHGO/ea_profile.json
* 2025-01-01 02:12:21 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sAHYQnsHGO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-01 02:12:21 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-02 02:12:13 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-02 02:12:14 (10313) [[32mINFO[0m] Script is up to date.
* 2025-01-02 02:12:15 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-02 02:12:15 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-02 02:12:15 (9238) [[32mINFO[0m] 
* 2025-01-02 02:12:18 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-02 02:12:18 (9238) [[32mINFO[0m] 
* 2025-01-02 02:12:19 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-02 02:12:19 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]         or
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]         compromise:
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-02 02:12:21 (9268) [[32mINFO[0m] 
* 2025-01-02 02:12:21 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-02 02:12:21 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-02 02:12:21 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-02 02:12:21 (9238) [[32mINFO[0m] 
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m]               : epel extras updates
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-02 02:12:21 (9268) [[32mINFO[0m] 
* 2025-01-02 02:12:21 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-02 02:12:21 (9238) [[32mINFO[0m] 
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-02 02:12:21 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]         or
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]         compromise:
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-02 02:12:22 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-02 02:12:22 (9268) [[32mINFO[0m] 
* 2025-01-02 02:12:22 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:22 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-02 02:12:22 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-02 02:12:22 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JJY6Md4yhP/ea_profile.json
* 2025-01-02 02:12:24 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JJY6Md4yhP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-02 02:12:24 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-03 02:12:15 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-03 02:12:16 (10313) [[32mINFO[0m] Script is up to date.
* 2025-01-03 02:12:17 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-03 02:12:17 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-03 02:12:17 (9238) [[32mINFO[0m] 
* 2025-01-03 02:12:20 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-03 02:12:20 (9238) [[32mINFO[0m] 
* 2025-01-03 02:12:20 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-03 02:12:20 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]         or
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]         compromise:
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-03 02:12:21 (9268) [[32mINFO[0m] 
* 2025-01-03 02:12:21 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-03 02:12:21 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-03 02:12:21 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-03 02:12:21 (9238) [[32mINFO[0m] 
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m]               : epel extras updates
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-03 02:12:21 (9268) [[32mINFO[0m] 
* 2025-01-03 02:12:21 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-03 02:12:21 (9238) [[32mINFO[0m] 
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-03 02:12:21 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]         or
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]         compromise:
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m] 
* 2025-01-03 02:12:22 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-03 02:12:22 (9268) [[32mINFO[0m] 
* 2025-01-03 02:12:22 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:22 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-03 02:12:22 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-03 02:12:22 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AStrEn7vGM/ea_profile.json
* 2025-01-03 02:12:25 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AStrEn7vGM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-03 02:12:25 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-03 15:46:43 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-03 15:46:44 (10313) [[32mINFO[0m] Script is up to date.
* 2025-01-03 15:46:45 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-03 15:46:45 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-03 15:46:45 (9238) [[32mINFO[0m] 
* 2025-01-03 15:46:47 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-03 15:46:47 (9238) [[32mINFO[0m] 
* 2025-01-03 15:46:47 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-03 15:46:47 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]         or
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]         compromise:
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-03 15:46:49 (9268) [[32mINFO[0m] 
* 2025-01-03 15:46:49 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-03 15:46:49 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-03 15:46:49 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-03 15:46:49 (9238) [[32mINFO[0m] 
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m]               : epel extras updates
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-03 15:46:49 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-03 15:46:49 (9268) [[32mINFO[0m] 
* 2025-01-03 15:46:49 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-03 15:46:49 (9238) [[32mINFO[0m] 
* 2025-01-03 15:46:50 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-03 15:46:50 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]         or
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]         compromise:
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m] 
* 2025-01-03 15:46:52 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-03 15:46:52 (9268) [[32mINFO[0m] 
* 2025-01-03 15:46:52 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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 15:46:52 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-03 15:46:52 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-03 15:46:52 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/prKlkQ3GNG/ea_profile.json
* 2025-01-03 15:46:57 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/prKlkQ3GNG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-03 15:46:57 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-04 02:12:41 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-04 02:12:42 (10313) [[32mINFO[0m] Script is up to date.
* 2025-01-04 02:12:43 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-04 02:12:43 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-04 02:12:43 (9238) [[32mINFO[0m] 
* 2025-01-04 02:12:45 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-04 02:12:45 (9238) [[32mINFO[0m] 
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]         or
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]         compromise:
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-04 02:12:46 (9268) [[32mINFO[0m] 
* 2025-01-04 02:12:46 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-04 02:12:46 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-04 02:12:46 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-04 02:12:46 (9238) [[32mINFO[0m] 
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m]               : epel extras updates
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-04 02:12:46 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-04 02:12:46 (9268) [[32mINFO[0m] 
* 2025-01-04 02:12:46 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-04 02:12:46 (9238) [[32mINFO[0m] 
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]         or
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]         compromise:
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-04 02:12:47 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-04 02:12:47 (9268) [[32mINFO[0m] 
* 2025-01-04 02:12:47 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:47 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-04 02:12:48 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-04 02:12:48 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FcHv7T1Lzc/ea_profile.json
* 2025-01-04 02:12:50 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FcHv7T1Lzc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-04 02:12:50 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-05 02:12:36 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-05 02:12:37 (10313) [[32mINFO[0m] Script is up to date.
* 2025-01-05 02:12:38 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-05 02:12:38 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-05 02:12:38 (9238) [[32mINFO[0m] 
* 2025-01-05 02:12:41 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-05 02:12:41 (9238) [[32mINFO[0m] 
* 2025-01-05 02:12:41 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-05 02:12:41 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]         or
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]         compromise:
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-05 02:12:43 (9268) [[32mINFO[0m] 
* 2025-01-05 02:12:43 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-05 02:12:43 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-05 02:12:43 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-05 02:12:43 (9238) [[32mINFO[0m] 
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m]               : epel extras updates
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-05 02:12:43 (9268) [[32mINFO[0m] 
* 2025-01-05 02:12:43 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-05 02:12:43 (9238) [[32mINFO[0m] 
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-05 02:12:43 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]         or
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]         compromise:
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m] 
* 2025-01-05 02:12:45 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-05 02:12:45 (9268) [[32mINFO[0m] 
* 2025-01-05 02:12:45 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-05 02:12:45 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-05 02:12:45 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-05 02:12:45 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5uHtSwUlXk/ea_profile.json
* 2025-01-05 02:12:48 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5uHtSwUlXk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-05 02:12:48 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-06 02:12:27 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-06 02:12:28 (10313) [[32mINFO[0m] Script is up to date.
* 2025-01-06 02:12:29 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-06 02:12:29 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-06 02:12:29 (9238) [[32mINFO[0m] 
* 2025-01-06 02:12:31 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-06 02:12:31 (9238) [[32mINFO[0m] 
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]         or
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]         compromise:
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-06 02:12:32 (9268) [[32mINFO[0m] 
* 2025-01-06 02:12:32 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-06 02:12:32 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-06 02:12:32 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-06 02:12:32 (9238) [[32mINFO[0m] 
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m]               : epel extras updates
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-06 02:12:32 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-06 02:12:32 (9268) [[32mINFO[0m] 
* 2025-01-06 02:12:32 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-06 02:12:32 (9238) [[32mINFO[0m] 
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]         or
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]         compromise:
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m] 
* 2025-01-06 02:12:33 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-06 02:12:33 (9268) [[32mINFO[0m] 
* 2025-01-06 02:12:33 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-06 02:12:33 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-06 02:12:33 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-06 02:12:33 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VUCJpOM0Gv/ea_profile.json
* 2025-01-06 02:12:36 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VUCJpOM0Gv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-06 02:12:36 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-07 02:13:26 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-07 02:13:27 (10313) [[32mINFO[0m] Script is up to date.
* 2025-01-07 02:13:28 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-07 02:13:28 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-07 02:13:28 (9238) [[32mINFO[0m] 
* 2025-01-07 02:13:30 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-07 02:13:30 (9238) [[32mINFO[0m] 
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]         or
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]         compromise:
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-07 02:13:31 (9268) [[32mINFO[0m] 
* 2025-01-07 02:13:31 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-07 02:13:31 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-07 02:13:31 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-07 02:13:31 (9238) [[32mINFO[0m] 
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m]               : epel extras updates
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-07 02:13:31 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-07 02:13:31 (9268) [[32mINFO[0m] 
* 2025-01-07 02:13:31 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-07 02:13:31 (9238) [[32mINFO[0m] 
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]         or
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]         compromise:
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m] 
* 2025-01-07 02:13:32 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-07 02:13:32 (9268) [[32mINFO[0m] 
* 2025-01-07 02:13:32 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:13:32 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-07 02:13:33 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-07 02:13:33 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LAoR4uh8iE/ea_profile.json
* 2025-01-07 02:13:35 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LAoR4uh8iE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-07 02:13:35 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-08 02:12:15 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-08 02:12:16 (10313) [[32mINFO[0m] Script is up to date.
* 2025-01-08 02:12:17 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-08 02:12:17 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-08 02:12:17 (9238) [[32mINFO[0m] 
* 2025-01-08 02:12:20 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-08 02:12:20 (9238) [[32mINFO[0m] 
* 2025-01-08 02:12:20 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-08 02:12:21 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] 12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]         or
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]         compromise:
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2025-01-08 02:12:51 (9268) [[32mINFO[0m] 
* 2025-01-08 02:12:51 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2025-01-08 02:12:51 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-08 02:12:51 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-08 02:12:51 (9238) [[32mINFO[0m] 
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m]               : epel extras updates
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-08 02:12:51 (9268) [[32mINFO[0m] 
* 2025-01-08 02:12:51 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-08 02:12:51 (9238) [[32mINFO[0m] 
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-08 02:12:51 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]         or
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]         compromise:
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-08 02:12:55 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-08 02:12:55 (9268) [[32mINFO[0m] 
* 2025-01-08 02:12:55 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:55 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-08 02:12:55 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-08 02:12:55 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/q1xYuD09tm/ea_profile.json
* 2025-01-08 02:13:35 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/q1xYuD09tm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-08 02:13:35 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-09 02:12:15 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-09 02:12:15 (10313) [[32mINFO[0m] Script is up to date.
* 2025-01-09 02:12:17 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-09 02:12:17 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-09 02:12:17 (9238) [[32mINFO[0m] 
* 2025-01-09 02:12:20 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-09 02:12:20 (9238) [[32mINFO[0m] 
* 2025-01-09 02:12:21 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-09 02:12:21 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m] 12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]         or
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]         compromise:
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2025-01-09 02:12:51 (9268) [[32mINFO[0m] 
* 2025-01-09 02:12:51 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2025-01-09 02:12:51 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-09 02:12:51 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-09 02:12:51 (9238) [[32mINFO[0m] 
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m]               : epel extras updates
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-09 02:12:51 (9268) [[32mINFO[0m] 
* 2025-01-09 02:12:51 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-09 02:12:51 (9238) [[32mINFO[0m] 
* 2025-01-09 02:12:51 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-09 02:12:52 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]         or
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]         compromise:
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m] 
* 2025-01-09 02:12:54 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-09 02:12:54 (9268) [[32mINFO[0m] 
* 2025-01-09 02:12:54 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:54 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-09 02:12:54 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-09 02:12:54 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2xK0FBO9Qv/ea_profile.json
* 2025-01-09 02:13:25 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2xK0FBO9Qv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-09 02:13:25 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-10 02:12:20 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-10 02:12:21 (10313) [[32mINFO[0m] Script is up to date.
* 2025-01-10 02:12:22 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-10 02:12:22 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-10 02:12:22 (9238) [[32mINFO[0m] 
* 2025-01-10 02:12:26 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-10 02:12:26 (9238) [[32mINFO[0m] 
* 2025-01-10 02:12:26 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-10 02:12:26 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]         or
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]         compromise:
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:28 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-10 02:12:28 (9268) [[32mINFO[0m] 
* 2025-01-10 02:12:28 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-10 02:12:28 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-10 02:12:28 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-10 02:12:28 (9238) [[32mINFO[0m] 
* 2025-01-10 02:12:29 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-10 02:12:29 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-10 02:12:29 (9251) [[32mINFO[0m]               : epel extras updates
* 2025-01-10 02:12:29 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-10 02:12:29 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-10 02:12:29 (9268) [[32mINFO[0m] 
* 2025-01-10 02:12:29 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-10 02:12:29 (9238) [[32mINFO[0m] 
* 2025-01-10 02:12:29 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-10 02:12:29 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]         or
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]         compromise:
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m] 
* 2025-01-10 02:12:31 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-10 02:12:31 (9268) [[32mINFO[0m] 
* 2025-01-10 02:12:31 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:31 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-10 02:12:31 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-10 02:12:31 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/C4w7azFpic/ea_profile.json
* 2025-01-10 02:13:11 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/C4w7azFpic/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-10 02:13:11 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-10 15:46:57 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-10 15:46:57 (10313) [[32mINFO[0m] Script is up to date.
* 2025-01-10 15:46:59 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-10 15:46:59 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-10 15:46:59 (9238) [[32mINFO[0m] 
* 2025-01-10 15:47:31 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-10 15:47:31 (9238) [[32mINFO[0m] 
* 2025-01-10 15:47:31 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-10 15:47:31 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m] 12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]         or
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]         compromise:
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2025-01-10 15:48:01 (9268) [[32mINFO[0m] 
* 2025-01-10 15:48:01 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
12: Timeout on http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: EA4/7/x86_64
* 2025-01-10 15:48:01 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-10 15:48:01 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-10 15:48:01 (9238) [[32mINFO[0m] 
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m]               : epel extras updates
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-10 15:48:01 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-10 15:48:02 (9268) [[32mINFO[0m] 
* 2025-01-10 15:48:02 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-10 15:48:02 (9238) [[32mINFO[0m] 
* 2025-01-10 15:48:02 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-10 15:48:02 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]         or
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]         compromise:
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m] 
* 2025-01-10 15:48:03 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-10 15:48:03 (9268) [[32mINFO[0m] 
* 2025-01-10 15:48:03 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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 15:48:03 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-10 15:48:03 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-10 15:48:03 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/otpYYilvvX/ea_profile.json
* 2025-01-10 15:49:10 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/otpYYilvvX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-10 15:49:10 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-11 02:12:48 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-11 02:12:49 (10313) [[32mINFO[0m] Script is up to date.
* 2025-01-11 02:12:50 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-11 02:12:50 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-11 02:12:50 (9238) [[32mINFO[0m] 
* 2025-01-11 02:12:53 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-11 02:12:53 (9238) [[32mINFO[0m] 
* 2025-01-11 02:12:53 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-11 02:12:53 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]         or
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]         compromise:
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-11 02:12:55 (9268) [[32mINFO[0m] 
* 2025-01-11 02:12:55 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-11 02:12:55 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-11 02:12:55 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-11 02:12:55 (9238) [[32mINFO[0m] 
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m]               : epel extras updates
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-11 02:12:55 (9268) [[32mINFO[0m] 
* 2025-01-11 02:12:55 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-11 02:12:55 (9238) [[32mINFO[0m] 
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-11 02:12:55 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]         or
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]         compromise:
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m] 
* 2025-01-11 02:12:57 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-11 02:12:57 (9268) [[32mINFO[0m] 
* 2025-01-11 02:12:57 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:57 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-11 02:12:57 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-11 02:12:57 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/48RkDrg0Ew/ea_profile.json
* 2025-01-11 02:13:28 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/48RkDrg0Ew/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-11 02:13:28 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-12 02:13:42 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-12 02:13:42 (10313) [[32mINFO[0m] Script is up to date.
* 2025-01-12 02:13:44 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-12 02:13:44 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-12 02:13:44 (9238) [[32mINFO[0m] 
* 2025-01-12 02:13:47 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-12 02:13:47 (9238) [[32mINFO[0m] 
* 2025-01-12 02:13:47 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-12 02:13:47 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]         or
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]         compromise:
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-12 02:13:48 (9268) [[32mINFO[0m] 
* 2025-01-12 02:13:48 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-12 02:13:48 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-12 02:13:48 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-12 02:13:48 (9238) [[32mINFO[0m] 
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m]               : epel extras updates
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-12 02:13:48 (9268) [[32mINFO[0m] 
* 2025-01-12 02:13:48 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-12 02:13:48 (9238) [[32mINFO[0m] 
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-12 02:13:48 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]         or
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]         compromise:
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m] 
* 2025-01-12 02:13:49 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-12 02:13:49 (9268) [[32mINFO[0m] 
* 2025-01-12 02:13:49 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:13:49 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-12 02:13:50 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-12 02:13:50 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WIT7Mo0bli/ea_profile.json
* 2025-01-12 02:13:59 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WIT7Mo0bli/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-12 02:13:59 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-13 02:12:41 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-13 02:12:42 (10313) [[32mINFO[0m] Script is up to date.
* 2025-01-13 02:12:43 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-13 02:12:43 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-13 02:12:43 (9238) [[32mINFO[0m] 
* 2025-01-13 02:12:46 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-13 02:12:46 (9238) [[32mINFO[0m] 
* 2025-01-13 02:12:46 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-13 02:12:46 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]         or
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]         compromise:
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:47 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-13 02:12:47 (9268) [[32mINFO[0m] 
* 2025-01-13 02:12:47 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-13 02:12:47 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-13 02:12:47 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-13 02:12:47 (9238) [[32mINFO[0m] 
* 2025-01-13 02:12:48 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-13 02:12:48 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-13 02:12:48 (9251) [[32mINFO[0m]               : epel extras updates
* 2025-01-13 02:12:48 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-13 02:12:48 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-13 02:12:48 (9268) [[32mINFO[0m] 
* 2025-01-13 02:12:48 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-13 02:12:48 (9238) [[32mINFO[0m] 
* 2025-01-13 02:12:48 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-13 02:12:48 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]         or
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]         compromise:
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m] 
* 2025-01-13 02:12:49 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-13 02:12:49 (9268) [[32mINFO[0m] 
* 2025-01-13 02:12:49 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:49 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-13 02:12:50 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-13 02:12:50 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5etQSdBkTh/ea_profile.json
* 2025-01-13 02:12:53 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5etQSdBkTh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-13 02:12:53 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-14 02:12:11 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-14 02:12:12 (10313) [[32mINFO[0m] Script is up to date.
* 2025-01-14 02:12:13 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-14 02:12:13 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-14 02:12:13 (9238) [[32mINFO[0m] 
* 2025-01-14 02:12:15 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-14 02:12:15 (9238) [[32mINFO[0m] 
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]         or
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]         compromise:
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-14 02:12:15 (9268) [[32mINFO[0m] 
* 2025-01-14 02:12:15 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-14 02:12:15 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-14 02:12:15 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-14 02:12:15 (9238) [[32mINFO[0m] 
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m]               : epel extras updates
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-14 02:12:15 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-14 02:12:16 (9268) [[32mINFO[0m] 
* 2025-01-14 02:12:16 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-14 02:12:16 (9238) [[32mINFO[0m] 
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]         or
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]         compromise:
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m] 
* 2025-01-14 02:12:16 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-14 02:12:16 (9268) [[32mINFO[0m] 
* 2025-01-14 02:12:16 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:16 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-14 02:12:16 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-14 02:12:16 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KBveW1DRm3/ea_profile.json
* 2025-01-14 02:12:18 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KBveW1DRm3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-14 02:12:18 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-15 02:12:59 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-15 02:12:59 (10313) [[32mINFO[0m] Script is up to date.
* 2025-01-15 02:13:01 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-15 02:13:01 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-15 02:13:01 (9238) [[32mINFO[0m] 
* 2025-01-15 02:13:03 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-15 02:13:03 (9238) [[32mINFO[0m] 
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]         or
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]         compromise:
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-15 02:13:03 (9268) [[32mINFO[0m] 
* 2025-01-15 02:13:03 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-15 02:13:03 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-15 02:13:03 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-15 02:13:03 (9238) [[32mINFO[0m] 
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m]               : epel extras updates
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-15 02:13:03 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-15 02:13:03 (9268) [[32mINFO[0m] 
* 2025-01-15 02:13:03 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-15 02:13:03 (9238) [[32mINFO[0m] 
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]         or
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]         compromise:
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m] 
* 2025-01-15 02:13:04 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-15 02:13:04 (9268) [[32mINFO[0m] 
* 2025-01-15 02:13:04 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:13:04 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-15 02:13:04 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-15 02:13:04 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/L0nj951uVJ/ea_profile.json
* 2025-01-15 02:13:06 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/L0nj951uVJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-15 02:13:06 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-16 02:12:09 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-16 02:12:10 (10313) [[32mINFO[0m] Script is up to date.
* 2025-01-16 02:12:11 (4071) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-16 02:12:11 (9237) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-16 02:12:11 (9238) [[32mINFO[0m] 
* 2025-01-16 02:12:13 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-16 02:12:13 (9238) [[32mINFO[0m] 
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]         or
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]         compromise:
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-16 02:12:13 (9268) [[32mINFO[0m] 
* 2025-01-16 02:12:13 (5793) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-16 02:12:13 (5794) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-16 02:12:13 (9237) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-16 02:12:13 (9238) [[32mINFO[0m] 
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m]               : epel extras updates
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-16 02:12:13 (9268) [[32mINFO[0m] 
* 2025-01-16 02:12:13 (9237) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-16 02:12:13 (9238) [[32mINFO[0m] 
* 2025-01-16 02:12:13 (9251) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]         or
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]         compromise:
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m] 
* 2025-01-16 02:12:14 (9251) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-16 02:12:14 (9268) [[32mINFO[0m] 
* 2025-01-16 02:12:14 (5803) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-16 02:12:14 (5804) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-16 02:12:14 (1992) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-16 02:12:14 (8362) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/He06lf5vIq/ea_profile.json
* 2025-01-16 02:12:18 (484) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/He06lf5vIq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-16 02:12:18 (448) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-17 02:12:39 (10291) [[32mINFO[0m] Self-update of script version 59 requested.
* 2025-01-17 02:12:40 (10296) [[32mINFO[0m] Newer version of script found. Downloading.
* 2025-01-17 02:12:41 (10305) [[32mINFO[0m] Script update to version 60 successful.
* 2025-01-17 02:12:42 (4156) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-17 02:12:42 (9400) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-17 02:12:42 (9401) [[32mINFO[0m] 
* 2025-01-17 02:12:44 (9400) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-17 02:12:44 (9401) [[32mINFO[0m] 
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]         or
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]         compromise:
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-17 02:12:44 (9431) [[32mINFO[0m] 
* 2025-01-17 02:12:44 (5878) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-17 02:12:44 (5879) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-17 02:12:44 (9400) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-17 02:12:44 (9401) [[32mINFO[0m] 
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m]               : epel extras updates
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-17 02:12:44 (9414) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-17 02:12:44 (9431) [[32mINFO[0m] 
* 2025-01-17 02:12:44 (9400) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-17 02:12:44 (9401) [[32mINFO[0m] 
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]         or
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]         compromise:
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m] 
* 2025-01-17 02:12:45 (9414) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-17 02:12:45 (9431) [[32mINFO[0m] 
* 2025-01-17 02:12:45 (5888) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-17 02:12:45 (5889) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-17 02:12:45 (2006) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-17 02:12:45 (8525) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NnE43zxXtJ/ea_profile.json
* 2025-01-17 02:12:48 (490) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NnE43zxXtJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-17 02:12:48 (454) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-17 15:46:38 (10458) [[32mINFO[0m] Self-update of script version 60 requested.
* 2025-01-17 15:46:38 (10480) [[32mINFO[0m] Script is up to date.
* 2025-01-17 15:46:39 (4156) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-17 15:46:39 (9400) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-17 15:46:39 (9401) [[32mINFO[0m] 
* 2025-01-17 15:46:42 (9400) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-17 15:46:42 (9401) [[32mINFO[0m] 
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m]         or
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:42 (9414) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]         compromise:
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-17 15:46:43 (9431) [[32mINFO[0m] 
* 2025-01-17 15:46:43 (5878) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-17 15:46:43 (5879) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-17 15:46:43 (9400) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-17 15:46:43 (9401) [[32mINFO[0m] 
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]               : epel extras updates
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-17 15:46:43 (9431) [[32mINFO[0m] 
* 2025-01-17 15:46:43 (9400) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-17 15:46:43 (9401) [[32mINFO[0m] 
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]         or
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]         compromise:
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] 
* 2025-01-17 15:46:43 (9414) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-17 15:46:43 (9431) [[32mINFO[0m] 
* 2025-01-17 15:46:43 (5888) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-17 15:46:43 (5889) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-17 15:46:44 (2006) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-17 15:46:44 (8525) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Zh2RkErvld/ea_profile.json
* 2025-01-17 15:47:47 (490) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Zh2RkErvld/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-17 15:47:47 (454) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-18 02:12:35 (10458) [[32mINFO[0m] Self-update of script version 60 requested.
* 2025-01-18 02:12:36 (10480) [[32mINFO[0m] Script is up to date.
* 2025-01-18 02:12:37 (4156) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-18 02:12:37 (9400) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-18 02:12:37 (9401) [[32mINFO[0m] 
* 2025-01-18 02:12:39 (9400) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-18 02:12:39 (9401) [[32mINFO[0m] 
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]         or
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]         compromise:
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-18 02:12:39 (9431) [[32mINFO[0m] 
* 2025-01-18 02:12:39 (5878) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-18 02:12:39 (5879) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-18 02:12:39 (9400) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-18 02:12:39 (9401) [[32mINFO[0m] 
* 2025-01-18 02:12:39 (9414) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]               : epel extras updates
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-18 02:12:40 (9431) [[32mINFO[0m] 
* 2025-01-18 02:12:40 (9400) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-18 02:12:40 (9401) [[32mINFO[0m] 
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]         or
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]         compromise:
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m] 
* 2025-01-18 02:12:40 (9414) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-18 02:12:40 (9431) [[32mINFO[0m] 
* 2025-01-18 02:12:40 (5888) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:40 (5889) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-18 02:12:40 (2006) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-18 02:12:40 (8525) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PNnjOsYkxo/ea_profile.json
* 2025-01-18 02:12:42 (490) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PNnjOsYkxo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-18 02:12:42 (454) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-19 02:13:04 (10458) [[32mINFO[0m] Self-update of script version 60 requested.
* 2025-01-19 02:13:05 (10480) [[32mINFO[0m] Script is up to date.
* 2025-01-19 02:13:06 (4156) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-19 02:13:06 (9400) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-19 02:13:06 (9401) [[32mINFO[0m] 
* 2025-01-19 02:13:08 (9400) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-19 02:13:08 (9401) [[32mINFO[0m] 
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]         or
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]         compromise:
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-19 02:13:08 (9431) [[32mINFO[0m] 
* 2025-01-19 02:13:08 (5878) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-19 02:13:08 (5879) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-19 02:13:08 (9400) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-19 02:13:08 (9401) [[32mINFO[0m] 
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m]               : epel extras updates
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-19 02:13:08 (9414) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-19 02:13:09 (9431) [[32mINFO[0m] 
* 2025-01-19 02:13:09 (9400) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-19 02:13:09 (9401) [[32mINFO[0m] 
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]         or
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]         compromise:
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m] 
* 2025-01-19 02:13:09 (9414) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-19 02:13:09 (9431) [[32mINFO[0m] 
* 2025-01-19 02:13:09 (5888) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:13:09 (5889) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-19 02:13:09 (2006) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-19 02:13:09 (8525) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qYYRP53HC0/ea_profile.json
* 2025-01-19 02:13:11 (490) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qYYRP53HC0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-19 02:13:11 (454) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-20 02:12:09 (10458) [[32mINFO[0m] Self-update of script version 60 requested.
* 2025-01-20 02:12:09 (10480) [[32mINFO[0m] Script is up to date.
* 2025-01-20 02:12:11 (4156) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-20 02:12:11 (9400) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-20 02:12:11 (9401) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9400) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-20 02:12:13 (9401) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         or
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         compromise:
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-20 02:12:13 (9431) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (5878) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-20 02:12:13 (5879) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-20 02:12:13 (9400) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-20 02:12:13 (9401) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]               : epel extras updates
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-20 02:12:13 (9431) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9400) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-20 02:12:13 (9401) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         or
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]         compromise:
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (9414) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-20 02:12:13 (9431) [[32mINFO[0m] 
* 2025-01-20 02:12:13 (5888) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:13 (5889) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-20 02:12:14 (2006) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-20 02:12:14 (8525) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EiXTajee8M/ea_profile.json
* 2025-01-20 02:12:46 (490) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EiXTajee8M/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-20 02:12:46 (454) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-21 02:12:30 (10458) [[32mINFO[0m] Self-update of script version 60 requested.
* 2025-01-21 02:12:30 (10480) [[32mINFO[0m] Script is up to date.
* 2025-01-21 02:12:32 (4156) [[33mWARN[0m] MariaDB is disabled. This must be enabled for the upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we recommend starting the process with MariaDB enabled.
* 2025-01-21 02:12:32 (9400) [[32mINFO[0m] Running: /usr/bin/yum list extras
* 2025-01-21 02:12:32 (9401) [[32mINFO[0m] 
* 2025-01-21 02:12:34 (9400) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-21 02:12:34 (9401) [[32mINFO[0m] 
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] Loading mirror speeds from cached hostfile
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]         or
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]         compromise:
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-21 02:12:34 (9431) [[32mINFO[0m] 
* 2025-01-21 02:12:34 (5878) [[33mWARN[0m] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-21 02:12:34 (5879) [[33mWARN[0m] Running "yum clean all" in an attempt to fix yum
* 2025-01-21 02:12:34 (9400) [[32mINFO[0m] Running: /usr/bin/yum clean all
* 2025-01-21 02:12:34 (9401) [[32mINFO[0m] 
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB105 base
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m]               : epel extras updates
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] Cleaning up list of fastest mirrors
* 2025-01-21 02:12:34 (9414) [[32mINFO[0m] Other repos take up 4.6 M of disk space (use --verbose for details)
* 2025-01-21 02:12:34 (9431) [[32mINFO[0m] 
* 2025-01-21 02:12:34 (9400) [[32mINFO[0m] Running: /usr/bin/yum makecache
* 2025-01-21 02:12:34 (9401) [[32mINFO[0m] 
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m] Determining fastest mirrors
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]  One of the configured repositories failed (Unknown),
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]         upstream. This is most often useful if you are using a newer
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]         distribution release than is supported by the repository (and the
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]         packages for the previous distribution release still work).
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]      3. Run the command with the repository temporarily disabled
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]             yum --disablerepo=<repoid> ...
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]         will then just ignore the repository until you permanently enable it
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]         again or use --enablerepo for temporary usage:
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]             yum-config-manager --disable <repoid>
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]         or
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]             subscription-manager repos --disable=<repoid>
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]         compromise:
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m] 
* 2025-01-21 02:12:35 (9414) [[32mINFO[0m] Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-21 02:12:35 (9431) [[32mINFO[0m] 
* 2025-01-21 02:12:35 (5888) [[31mERROR[0m] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a 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:12:35 (5889) [[31mERROR[0m] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
* 2025-01-21 02:12:35 (2006) [[32mINFO[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-21 02:12:35 (8525) [[32mINFO[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0QXCGl_J_h/ea_profile.json
* 2025-01-21 02:12:38 (490) [[33mWARN[0m] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0QXCGl_J_h/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527.
* 2025-01-21 02:12:38 (454) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-05-09 02:12:22 (10458) [[32mINFO[0m] Self-update of script version 60 requested.
* 2025-05-09 02:12:23 (10463) [[32mINFO[0m] Newer version of script found. Downloading.
* 2025-05-09 02:12:24 (10472) [[32mINFO[0m] Script update to version 65 successful.
* 2025-05-09 02:12:25 (10029) [[32mINFO[0m] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only
* 2025-05-09 02:12:25 (10030) [[32mINFO[0m] 
* 2025-05-09 02:13:04 (10060) [[32mINFO[0m] 
* 2025-05-09 02:13:04 (124) [[31mERROR[0m] Tried to sync version /etc/cpanel/TIERS.json file but failed: Failed to download signature at URL 'http://1.mirror.ir.cdn.mycache.org/cpanelsync/TIERS.json.asc'.
* 2025-05-09 02:13:04 (535) [[33mWARN[0m] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 7287.
* 2025-05-09 02:13:04 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-06-22 05:52:21 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2025-06-22 05:53:12 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID jq2cwf) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Temporary failure in name resolution
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x29b35a0), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x29b3498)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x29b35a0), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2999940)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2999940)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2999940)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x29997c0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x29997c0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x292bbf8), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x292bbf8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x292bbf8), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x292bbf8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2025-06-22 05:53:12 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-06-23 05:49:34 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2025-06-23 05:50:25 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 89s4rr) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Temporary failure in name resolution
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x3547c28), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x35617c8)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x3547c28), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x3547bb0)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x3547bb0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x3547bb0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3548408)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3548408)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x34dc838), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x34dc838)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x34dc838), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x34dc838)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2025-06-23 05:50:25 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-06-24 05:48:16 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2025-06-24 05:49:07 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID ry5vbp) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Temporary failure in name resolution
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x3fcd318), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3fd0ed8)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x3fcd318), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x3fb30f0)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x3fb30f0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x3fb30f0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3fb3258)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3fb3258)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3f47c18), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3f47c18)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3f47c18), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3f47c18)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2025-06-24 05:49:07 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-06-25 05:48:40 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2025-06-25 05:49:31 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 7vece6) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Temporary failure in name resolution
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x426c670), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x4285da8)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x426c670), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x4285988)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x4285988)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x4285988)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x426c040)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x426c040)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x41ffec8), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x41ffec8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x41ffec8), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x41ffec8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2025-06-25 05:49:31 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-01 08:53:35 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-01 08:54:37 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID bc6unh) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2b578e8), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2b6f758)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2b578e8), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2afe710)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2afe710)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2afe710)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2b2e550)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2b2e550)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2813370), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2813370)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2813370), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2813370)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-01 08:54:37 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-02 08:32:59 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-02 08:34:01 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID hyvcdp) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2f3cae8), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2f546c8)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2f3cae8), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2f3c800)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2f3c800)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2f3c800)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2f3c668)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2f3c668)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2ed0ef8), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2ed0ef8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2ed0ef8), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2ed0ef8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-02 08:34:01 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-03 08:31:18 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-03 08:32:20 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 2485eq) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x3eaf318), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3ec6ac8)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x3eaf318), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x3e927b0)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x3e927b0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x3e927b0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3eaf180)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3eaf180)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3e430d0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3e430d0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3e430d0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3e430d0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-03 08:32:20 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-03 22:06:32 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-03 22:07:34 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID kk2a49) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x395cee0), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x39765d0)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x395cee0), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x395c868)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x395c868)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x395c868)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3a01f18)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3a01f18)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x38eede0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x38eede0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x38eede0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x38eede0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-03 22:07:34 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-04 08:33:52 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-04 08:34:54 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID ggpy6v) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x408fae8), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x4092e78)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x408fae8), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x4077ac8)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x4077ac8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x4077ac8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x4077c78)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x4077c78)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x400bfc8), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x400bfc8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x400bfc8), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x400bfc8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-04 08:34:54 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-05 08:32:21 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-05 08:33:23 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID rvadrz) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x3d18570), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3d31700)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x3d18570), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x3d17a30)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x3d17a30)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x3d17a30)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3cbee40)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3cbee40)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x39d2610), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x39d2610)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x39d2610), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x39d2610)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-05 08:33:23 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-06 08:32:28 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-06 08:33:30 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID hfpkz5) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x36733e0), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x36732d8)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x36733e0), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x366c220)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x366c220)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x366c220)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3655a10)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3655a10)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x35e9c48), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x35e9c48)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x35e9c48), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x35e9c48)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-06 08:33:30 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-07 08:32:45 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-07 08:33:47 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID hhr9v5) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x3dba140), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3dd3840)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x3dba140), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x3db9378)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x3db9378)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x3db9378)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3db99a8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3db99a8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3a73380), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3a73380)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3a73380), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3a73380)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-07 08:33:47 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-08 08:31:29 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-08 08:32:31 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID t48r73) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x45699a8), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x4569b40)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x45699a8), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x4568eb0)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x4568eb0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x4568eb0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x454fa28)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x454fa28)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x4208680), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x4208680)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x4208680), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x4208680)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-08 08:32:31 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-09 08:32:00 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-09 08:33:02 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID hy2stq) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x362d4b8), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3645b30)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x362d4b8), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x362d530)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x362d530)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x362d530)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x362d380)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x362d380)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x32e5550), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x32e5550)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x32e5550), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x32e5550)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-09 08:33:02 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-10 08:32:27 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-10 08:33:29 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID etv77b) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2e68d60), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2e81fd8)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2e68d60), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2e68508)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2e68508)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2e68508)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2e55ab8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2e55ab8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2b21510), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2b21510)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2b21510), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2b21510)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-10 08:33:29 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-10 22:05:58 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-10 22:07:00 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID m63nby) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x3a75060), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3a8e878)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x3a75060), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x3a748e0)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x3a748e0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x3a748e0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3a74a48)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3a74a48)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3a093f0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3a093f0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3a093f0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3a093f0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-10 22:07:00 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-11 08:31:17 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-11 08:32:19 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID ft5vmv) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x4774ee8), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x478c6f0)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x4774ee8), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x4774900)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x4774900)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x4774900)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x4774858)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x4774858)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x442fae0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x442fae0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x442fae0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x442fae0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-11 08:32:19 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-12 08:33:07 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-12 08:34:09 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID mg777a) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x3d32248), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3d35c20)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x3d32248), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x3d1a608)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x3d1a608)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x3d1a608)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3d1a530)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3d1a530)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x39d2f70), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x39d2f70)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x39d2f70), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x39d2f70)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-12 08:34:09 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-13 08:30:29 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-13 08:31:31 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID qmezef) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x4097a38), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x40b2870)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x4097a38), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x40aef38)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x40aef38)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x40aef38)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x4097030)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x4097030)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x402b650), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x402b650)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x402b650), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x402b650)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-13 08:31:31 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-14 08:31:02 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-14 08:32:04 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID f4s2bx) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2c4d6b8), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2c65300)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2c4d6b8), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2c4d250)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2c4d250)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2c4d250)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2c48b30)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2c48b30)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2907650), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2907650)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2907650), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2907650)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-14 08:32:04 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-15 08:31:55 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-15 08:32:57 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID yfrnc7) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2b54788), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2b57fe8)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2b54788), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2b54350)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2b54350)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2b54350)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2b3a4b8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2b3a4b8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2acea78), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2acea78)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2acea78), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2acea78)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-15 08:32:57 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-16 08:33:13 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-16 08:34:15 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID kzaa92) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x3809648), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3824df0)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x3809648), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x3809690)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x3809690)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x3809690)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x37ed808)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x37ed808)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x34c3a70), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x34c3a70)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x34c3a70), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x34c3a70)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-16 08:34:15 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-17 08:31:38 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-17 08:32:40 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID m98fww) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x304c4b0), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x304ca38)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x304c4b0), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x3034558)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x3034558)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x3034558)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x30347e0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x30347e0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2fc8948), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2fc8948)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2fc8948), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2fc8948)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-17 08:32:40 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-17 22:07:07 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-17 22:08:09 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 8zzsp5) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x3af4850), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3b0ddc0)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x3af4850), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x3af4070)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x3af4070)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x3af4070)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3af41c0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3af41c0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3a86428), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3a86428)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3a86428), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3a86428)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-17 22:08:09 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-18 08:33:58 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-18 08:35:01 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 86cza4) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2e105e8), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2e17560)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2e105e8), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2dff278)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2dff278)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2dff278)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2dfefd8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2dfefd8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2d93b78), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2d93b78)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2d93b78), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2d93b78)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-18 08:35:01 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-19 08:31:14 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-19 08:32:16 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID brbwsw) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x361fef8), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x361ff40)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x361fef8), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x36047a0)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x36047a0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x36047a0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3604680)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3604680)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x32bf4b0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x32bf4b0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x32bf4b0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x32bf4b0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-19 08:32:16 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-20 08:30:17 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-20 08:31:19 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID ez8mhs) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x29ee6a0), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2a092b8)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x29ee6a0), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x29ed9e0)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x29ed9e0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x29ed9e0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2994d48)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2994d48)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2980228), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2980228)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2980228), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2980228)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-20 08:31:19 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-21 08:31:20 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-21 08:32:23 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID aav4gm) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x41aa538), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x41c26d0)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x41aa538), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x41aa370)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x41aa370)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x41aa370)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x41aa4c0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x41aa4c0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3e64c30), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3e64c30)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3e64c30), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3e64c30)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-21 08:32:23 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-22 08:30:35 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-22 08:31:37 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID kf8ksb) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x4034ad8), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x4035210)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x4034ad8), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x401cd90)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x401cd90)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x401cd90)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x401ccb8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x401ccb8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3fb1600), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3fb1600)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3fb1600), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3fb1600)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-22 08:31:37 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-23 08:37:39 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-23 08:38:41 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 348p3v) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x440e338), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x440e650)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x440e338), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x3f03000)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x3f03000)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x3f03000)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x42947e0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x42947e0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x4388e70), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x4388e70)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x4388e70), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x4388e70)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-23 08:38:41 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-24 08:31:24 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-24 08:32:26 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 6ttmcv) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x3a45938), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3a425d0)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x3a45938), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x3a42378)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x3a42378)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x3a42378)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3a29e68)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3a29e68)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x36e35a0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x36e35a0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x36e35a0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x36e35a0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-24 08:32:26 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-24 22:05:07 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-24 22:06:09 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID d2ur2b) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x4106fe0), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x4107400)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x4106fe0), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x40eef88)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x40eef88)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x40eef88)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x40d4bb0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x40d4bb0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3da76a0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3da76a0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3da76a0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3da76a0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-24 22:06:09 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-25 08:31:30 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-25 08:32:32 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID xnvjem) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x3f62a50), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3f62af8)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x3f62a50), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x3f4a5e0)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x3f4a5e0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x3f4a5e0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3ea3540)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3ea3540)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3c03ad0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3c03ad0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3c03ad0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3c03ad0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-25 08:32:32 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-26 08:32:49 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-26 08:33:52 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID ph8cpa) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x40623e0), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x407c220)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x40623e0), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x4061d08)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x4061d08)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x4061d08)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x4061e70)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x4061e70)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3ff4b30), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3ff4b30)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3ff4b30), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3ff4b30)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-26 08:33:52 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-27 08:32:48 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-27 08:33:51 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID dgakkm) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2a16018), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2a42cc8)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2a16018), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2a2b370)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2a2b370)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2a2b370)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2a2b430)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2a2b430)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x26e5520), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x26e5520)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x26e5520), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x26e5520)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-27 08:33:51 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-28 08:31:59 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-28 08:33:01 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID qm674q) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x3b1c198), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3b1fd90)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x3b1c198), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x3b023e0)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x3b023e0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x3b023e0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3b02440)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3b02440)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3a947e0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3a947e0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3a947e0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3a947e0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-28 08:33:01 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-29 08:33:54 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-29 08:34:57 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID yvps55) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x429c5a0), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x429c720)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x429c5a0), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x4284658)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x4284658)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x4284658)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x4284670)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x4284670)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x4218c80), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x4218c80)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x4218c80), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x4218c80)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-29 08:34:57 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-04-30 08:33:43 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-04-30 08:34:45 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 5jaq25) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x3dcbf90), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3dcc398)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x3dcbf90), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x3db4b98)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x3db4b98)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x3db4b98)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3db42c8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3db42c8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3d48388), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3d48388)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3d48388), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3d48388)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-04-30 08:34:45 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-05-01 08:32:22 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-05-01 08:33:24 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID y9jsct) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2b71d50), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2b897d8)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2b71d50), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2b71618)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2b71618)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2b71618)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2b71588)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2b71588)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x282b7d0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x282b7d0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x282b7d0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x282b7d0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-05-01 08:33:24 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-05-01 22:05:42 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-05-01 22:06:44 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID sfxj4r) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x3f64958), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3f64df0)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x3f64958), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x3ef3f88)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x3ef3f88)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x3ef3f88)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3f4c9b8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3f4c9b8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3c06e20), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3c06e20)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3c06e20), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3c06e20)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-05-01 22:06:44 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-05-02 08:32:39 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-05-02 08:33:41 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID mzhmn6) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x30b2278), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x30cced8)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x30b2278), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x30b1b40)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x30b1b40)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x30b1b40)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x30b2290)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x30b2290)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3045f88), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3045f88)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3045f88), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3045f88)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-05-02 08:33:41 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-05-03 08:32:42 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-05-03 08:33:44 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 3bmtq8) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x403d268), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x4040988)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x403d268), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x40253a8)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x40253a8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x40253a8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3efa920)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3efa920)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3cde630), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3cde630)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3cde630), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3cde630)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-05-03 08:33:44 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-05-04 08:33:38 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-05-04 08:34:40 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID jvmrbp) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x40287b8), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x40288f0)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x40287b8), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x4010948)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x4010948)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x4010948)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x4010960)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x4010960)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3fa2f88), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3fa2f88)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3fa2f88), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3fa2f88)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-05-04 08:34:40 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-05-05 08:31:42 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-05-05 08:32:44 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 45ueuc) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x38f57f0), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3910a90)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x38f57f0), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x38f52f8)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x38f52f8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x38f52f8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x38d48b0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x38d48b0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3887700), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3887700)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3887700), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3887700)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-05-05 08:32:44 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-05-06 08:31:25 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-05-06 08:32:27 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID ybu4df) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2fefa10), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3009a68)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2fefa10), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2fef920)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2fef920)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2fef920)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2fef788)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2fef788)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2f81d68), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2f81d68)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2f81d68), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2f81d68)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-05-06 08:32:27 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-05-07 08:32:53 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-05-07 08:33:56 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID enuvnv) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x31c0348), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x31da1a8)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x31c0348), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x31c0318)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x31c0318)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x31c0318)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x31d34e8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x31d34e8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2e7a2f0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2e7a2f0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2e7a2f0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2e7a2f0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-05-07 08:33:56 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-05-08 08:25:25 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-05-08 08:26:27 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID vega6v) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x42aa738), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x42c21b0)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x42aa738), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x3a7a160)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x3a7a160)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x3a7a160)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x42aa210)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x42aa210)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3f632b0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3f632b0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3f632b0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3f632b0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-05-08 08:26:27 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-05-08 22:07:18 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-05-08 22:08:21 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID pvq7mg) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x36caa50), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x36e6018)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x36caa50), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x36ca8d0)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x36ca8d0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x36ca8d0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x36caa80)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x36caa80)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x365ced8), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x365ced8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x365ced8), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x365ced8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-05-08 22:08:21 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-05-09 08:32:29 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-05-09 08:33:31 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 3ppkyj) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x46182d8), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x46300d0)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x46182d8), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x4618158)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x4618158)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x4618158)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x46180c8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x46180c8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x42d1a30), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x42d1a30)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x42d1a30), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x42d1a30)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-05-09 08:33:31 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-05-10 00:19:08 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-05-10 00:20:11 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 8zyex4) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Name or service not known
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2a514f8), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2a51750)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2a514f8), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2a33dd8)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2a33dd8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2a33dd8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2a33cb8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2a33cb8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x26ee988), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x26ee988)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x26ee988), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x26ee988)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-05-10 00:20:11 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-05-30 22:42:00 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-05-30 22:58:02 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID h7vtq5) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x38c2240), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x38dbf58)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x38c2240), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x38c22b8)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x38c22b8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x38c22b8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x38c2150)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x38c2150)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x357bf78), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x357bf78)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x357bf78), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x357bf78)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-05-30 22:58:02 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-05-31 08:30:05 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-05-31 08:46:07 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID ek5p3t) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2f8ceb8), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2fa6f28)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2f8ceb8), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2f8cd38)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2f8cd38)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2f8cd38)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2f8cca8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2f8cca8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2c461a0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2c461a0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2c461a0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2c461a0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-05-31 08:46:07 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-01 08:29:14 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-01 08:45:16 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID cdrgu7) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2f580d0), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2f720c8)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2f580d0), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2f57ea8)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2f57ea8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2f57ea8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2f57ec0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2f57ec0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2c0f760), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2c0f760)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2c0f760), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2c0f760)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-01 08:45:16 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-02 08:30:17 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-02 08:46:19 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID tnpg8c) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2eff8f0), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2eff7d0)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2eff8f0), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2ee76d8)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2ee76d8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2ee76d8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2ee78b8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2ee78b8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2e7bd08), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2e7bd08)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2e7bd08), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2e7bd08)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-02 08:46:19 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-03 08:30:09 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-03 08:46:11 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 6sfddx) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x46b0a38), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x46c85e0)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x46b0a38), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x46a62e8)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x46a62e8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x46a62e8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x46b0708)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x46b0708)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x46450c0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x46450c0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x46450c0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x46450c0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-03 08:46:11 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-04 08:28:22 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-04 08:44:24 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 7pdysm) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x3c1c6a0), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3c1caf0)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x3c1c6a0), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x3c1c718)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x3c1c718)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x3c1c718)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3c04bc8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3c04bc8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x38bfad0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x38bfad0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x38bfad0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x38bfad0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-04 08:44:24 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-05 08:29:53 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-05 08:46:15 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID ctrn62) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2fab930), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2fabcd8)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2fab930), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2f90298)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2f90298)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2f90298)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2f90220)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2f90220)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2f24ab8), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2f24ab8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2f24ab8), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2f24ab8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-05 08:46:15 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-05 22:03:52 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-05 22:20:04 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID yqq6gy) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x411cfc8), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x41192e8)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x411cfc8), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x40ffaf8)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x40ffaf8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x40ffaf8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x40ff888)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x40ff888)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3db9560), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3db9560)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3db9560), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3db9560)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-05 22:20:04 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-06 08:31:42 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-06 08:48:03 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID wyaatm) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x428c2c8), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x428c430)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x428c2c8), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x4274a40)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x4274a40)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x4274a40)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x4274350)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x4274350)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x4206c50), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x4206c50)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x4206c50), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x4206c50)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-06 08:48:03 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-07 08:33:31 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-07 08:49:33 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 6yga7h) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2f88a28), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2fa17a0)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2f88a28), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2f0ff58)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2f0ff58)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2f0ff58)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2f87ca8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2f87ca8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2c42820), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2c42820)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2c42820), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2c42820)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-07 08:49:33 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-08 08:26:32 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-08 08:42:34 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID z53f9u) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2bf9b88), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2c134d0)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2bf9b88), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2b75630)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2b75630)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2b75630)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2bf9be8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2bf9be8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x28b3780), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x28b3780)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x28b3780), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x28b3780)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-08 08:42:34 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-09 08:29:18 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-09 08:45:20 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID nnb6h5) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x426cb40), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x428a020)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x426cb40), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x426c798)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x426c798)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x426c798)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x426c3a8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x426c3a8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x41ff310), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x41ff310)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x41ff310), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x41ff310)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-09 08:45:20 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-10 08:30:44 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-10 08:46:46 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID aqvf6w) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x33fa578), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x33fd878)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x33fa578), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x33e20d8)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x33e20d8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x33e20d8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x33e1d78)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x33e1d78)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x309e0c0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x309e0c0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x309e0c0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x309e0c0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-10 08:46:46 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-11 08:29:15 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-11 08:45:17 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID cut5m6) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x42d7c10), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x42ef958)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x42d7c10), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x42d7718)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x42d7718)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x42d7718)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x42d7700)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x42d7700)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3f93270), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3f93270)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3f93270), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3f93270)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-11 08:45:17 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-12 08:25:26 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-12 08:41:28 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID h4x2rb) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x36628e0), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3662760)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x36628e0), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x364a5a8)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x364a5a8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x364a5a8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x36e5638)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x36e5638)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x35dcb88), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x35dcb88)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x35dcb88), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x35dcb88)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-12 08:41:28 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-12 22:02:52 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-12 22:18:54 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 5457s7) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2fa68f0), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2fa6c38)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2fa68f0), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2f8ece8)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2f8ece8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2f8ece8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2f8eca0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2f8eca0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2c4c090), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2c4c090)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2c4c090), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2c4c090)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-12 22:18:54 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-13 08:31:44 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-13 08:47:46 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID yp2y4u) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x337bb30), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x3395620)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x337bb30), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x337b440)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x337b440)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x337b440)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x337b488)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x337b488)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x3034280), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x3034280)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x3034280), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x3034280)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-13 08:47:46 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-14 08:28:11 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-14 08:44:12 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 2b42d6) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x30a8c48), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x30a91b8)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x30a8c48), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x307f278)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x307f278)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x307f278)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x30910a0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x30910a0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2d48dd0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2d48dd0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2d48dd0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2d48dd0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-14 08:44:13 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-15 08:28:58 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-15 08:45:00 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 55cryn) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2ef21f0), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x2f0a2e0)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x2ef21f0), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x2ef2448)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x2ef2448)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x2ef2448)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2ef2820)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2ef2820)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2e86828), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2e86828)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2e86828), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2e86828)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-15 08:45:00 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-16 08:30:50 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-16 08:46:52 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 2u755f) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x439ca30), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x43b6020)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x439ca30), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x439c190)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x439c190)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x439c190)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3ea9dc0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3ea9dc0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x4330940), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x4330940)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x4330940), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x4330940)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-16 08:46:52 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-17 08:30:59 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-17 08:47:01 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID y2y9vk) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x31eec40), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x31eeb68)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x31eec40), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x31d4eb0)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x31d4eb0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x31d4eb0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x3057bd8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x3057bd8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x2e8f680), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x2e8f680)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x2e8f680), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x2e8f680)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-17 08:47:01 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-18 08:30:16 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-18 08:46:18 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID yywpzp) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x294b5a0), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x294b210)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x294b5a0), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x294b3d8)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x294b3d8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x294b3d8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x2931400)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x2931400)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x25e9e70), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x25e9e70)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x25e9e70), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x25e9e70)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-18 08:46:18 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-19 08:29:54 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-19 08:45:56 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID zzzyzs) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x35ba4b0), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x35d44f0)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x35ba4b0), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x35ba8d0)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x35ba8d0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x35ba8d0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x35ba930)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x35ba930)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x354e770), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x354e770)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x354e770), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x354e770)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-19 08:45:56 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-19 22:03:21 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-19 22:19:23 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID u2y4q2) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x378dc48), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x37a8e18)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x378dc48), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x378da80)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x378da80)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x378da80)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x378d780)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x378d780)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x371fd80), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x371fd80)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x371fd80), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x371fd80)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-19 22:19:23 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-20 08:28:58 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-20 08:44:59 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID eyvu3j) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x43efee8), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x440d580)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x43efee8), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x43d6fd0)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x43d6fd0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x43d6fd0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x43ef990)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x43ef990)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x40a9240), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x40a9240)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x40a9240), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x40a9240)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-20 08:44:59 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2026-06-21 08:24:29 (11091) [[32mINFO[0m] Self-update of script version 65 requested.
* 2026-06-21 08:40:31 (535) [[33mWARN[0m] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID wp6hyn) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> âGETâ request to âhttps://raw.githubusercontent.com/cpanel/elevate/release/versionâ because of an error: Could not connect to 'raw.githubusercontent.com:443': Connection timed out
 at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137.
	Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x296af38), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x296b130)) called at (eval 11) line 6
	HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x296af38), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 10102
	Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x28bfec8)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259
	Simple::Accessor::__ANON__(Elevate::Script=HASH(0x28bfec8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 10112
	Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x28bfec8)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2411
	Elevate::Components::ElevateScript::_is_up_to_date(Elevate::Components::ElevateScript=HASH(0x29f3938)) called at /usr/local/cpanel/scripts/elevate-cpanel line 2387
	Elevate::Components::ElevateScript::check(Elevate::Components::ElevateScript=HASH(0x29f3938)) called at /usr/local/cpanel/scripts/elevate-cpanel line 580
	Elevate::Components::_check_single_blocker(Elevate::Components=HASH(0x260cfc0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 568
	Elevate::Components::_check_all_blockers(Elevate::Components=HASH(0x260cfc0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 527
	Elevate::Components::_has_blockers(Elevate::Components=HASH(0x260cfc0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 472
	Elevate::Components::check(Elevate::Components=HASH(0x260cfc0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 11041
	cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 10981
* 2026-06-21 08:40:31 (476) [[33mWARN[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
